yw1573/BiliDown
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: remove duplicate timestamp in log output

Browse Source 
禁用 log 默认时间戳，避免日志输出重复时间

Co-Authored-By: AI
This commit is contained in:
yw1573
2026-04-09 11:06:17 +08:00
parent 9b73ea9b68
commit 36d089705a
4 changed files with 5 additions and 179 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/CLAUDE.md
-15
View File
@@ -1,15 +0,0 @@
# 我是简体中文用户
# 我是简体中文用户
# 我是简体中文用户
# 这是windows系统，不是linux，也不是wsl
# 这是windows系统，不是linux，也不是wsl
# 这是windows系统，不是linux，也不是wsl
# 涉及到各种图的画法，使用`mermaid`
# 代码注释使用中文。utf-8编码
@configs/git-commit.md
@configs/env.md
.claude/configs/env.md
-35
View File
@@ -1,35 +0,0 @@
# environment
**The current system is Windows.**
## go env:
**C:\Program Files\Go\bin**
## git env:
**C:\Program Files\PortableGit\bin**
## python env:
**C:\Program Files\Python314**
**C:\Program Files\Python314\Scripts**
**Please locate the venv or .venv directory in your project to create a Python virtual environment.**
## node env
**C:\Program Files\nodejs**
## nmap env:
**C:\Program Files (x86)\Nmap**
## sqliet3 env:
**C:\Program Files\sqlite-tools-win-x64-3510300**
## curl env:
**C:\Program Files\curl-8.19.0_2-win64-mingw\bin**
.claude/configs/git-commit.md
-129
View File
@@ -1,129 +0,0 @@
# 我是中文简体用户
# Commit Message Format
We have very precise rules over how our Git commit messages must be formatted.
This format leads to **easier to read commit history** and makes it analyzable for changelog generation.
Each commit message consists of a **header**, a **body**, and a **footer**.
```
<header>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
```
The `header` is mandatory and must conform to the [Commit Message Header](#commit-header) format.
The `body` is mandatory for all commits except for those of type "docs".
When the body is present it must be at least 20 characters long and must conform to the [Commit Message Body](#commit-body) format.
The `footer` is optional. The [Commit Message Footer](#commit-footer) format describes what the footer is used for and the structure it must have.
## Commit Message Header
```
<type>(<scope>): <short summary>
│ │ │
│ │ └─⫸ Summary in present tense. Not capitalized. No period at the end.
│ │
│ └─⫸ Commit Scope: anything module
│
│
│
│
│
└─⫸ Commit Type: build|ci|docs|feat|fix|perf|refactor|test
```
The `<type>` and `<summary>` fields are mandatory, the `(<scope>)` field is optional.
### Type
Must be one of the following:
| Type | Description |
| ------------ | --------------------------------------------------------------------------------------------------- |
| **build** | Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm) |
| **ci** | Changes to our CI configuration files and scripts (examples: Github Actions, SauceLabs) |
| **docs** | Documentation only changes |
| **feat** | A new feature |
| **fix** | A bug fix |
| **perf** | A code change that improves performance |
| **refactor** | A code change that neither fixes a bug nor adds a feature |
| **test** | Adding missing tests or correcting existing tests |
### Scope
The scope should be the name of the module affected (as perceived by the person reading the changelog generated from commit messages).
There are currently a few exceptions to the "use package name" rule:
- `dev-infra`: used for dev-infra related changes within the directories /scripts and /tools
- `docs-infra`: used for infrastructure changes to the docs-app (angular.dev) within the `/adev` directory, such as application code, tooling, or configuration. **For modifications to documentation content (e.g., editing a `.md` file), use `docs:` without a scope instead.**
- `migrations`: used for changes to the `ng update` migrations.
- none/empty string: useful for `test` and `refactor` changes that are done across all packages (e.g. `test: add missing unit tests`) and for docs changes that are not related to a specific package (e.g. `docs: fix typo in tutorial`).
### Summary
Use the summary field to provide a succinct description of the change:
- use the imperative, present tense: "change" not "changed" nor "changes"
- don't capitalize the first letter
- no dot (.) at the end
## Commit Message Body
Just as in the summary, use the imperative, present tense: "fix" not "fixed" nor "fixes".
Explain the motivation for the change in the commit message body. This commit message should explain _why_ you are making the change.
You can include a comparison of the previous behavior with the new behavior in order to illustrate the impact of the change.
## Commit Message Footer
The footer can contain information about breaking changes and deprecations and is also the place to reference GitHub issues and other PRs that this commit closes or is related to.
For example:
```
BREAKING CHANGE: <breaking change summary>
<BLANK LINE>
<breaking change description + migration instructions>
<BLANK LINE>
<BLANK LINE>
Fixes #<issue number>
```
or
```
DEPRECATED: <what is deprecated>
<BLANK LINE>
<deprecation description + recommended update path>
<BLANK LINE>
<BLANK LINE>
Closes #<pr number>
```
Breaking Change section should start with the phrase `BREAKING CHANGE: ` followed by a _brief_ summary of the breaking change, a blank line, and a detailed description of the breaking change that also includes migration instructions.
Similarly, a Deprecation section should start with `DEPRECATED: ` followed by a short description of what is deprecated, a blank line, and a detailed description of the deprecation that also mentions the recommended update path.
## Revert commits
If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit.
The content of the commit message body should contain:
- information about the SHA of the commit being reverted in the following format: `This reverts commit <SHA>`,
- a clear description of the reason for reverting the commit message.
## 在Body中最后一行添加`Co-Authored-By: AI`
# 尽可能的使用简体中文
internal/logger/logger.go
+5
View File
@@ -14,6 +14,11 @@ var (
mu sync.Mutex
)
func init() {
// 禁用 log 默认的时间戳前缀
log.SetFlags(0)
}
// SetLevel 设置日志级别
func SetLevel(l string) {
mu.Lock()