rust-lang / rust-lang/rust-analyzer
Non-informative INFO logs about GlobalState task queue length
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
rust-analyzer version: rust-analyzer version: 0.3.1896-standalone
rustc version: rustc 1.76.0 (07dca489a 2024-02-04)
relevant settings: None
repository link (if public, optional): N/A
code snippet to reproduce:
Open VS Code,
Hover your mouse cursor over "rust-analyzer" until the context menu appears,
Select "Open Logs"
Observe:
Would it be possible to tone down these info-level log messages which don't convey any information to increase the signal to noise ratio? Often when there's an issue one must scroll past a lot of these.
Maybe I set the log level to info because I needed to debug rust-analyzer not analyzing my projects. However, these do not seem worthy of "INFO" ... maybe "DEBUG" or "TRACE" would be more appropriate for these specific messages?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the log output in VS Code by opening rust-analyzer's logs, then search the rust-analyzer code for the GlobalState task queue length messages. Confirm which messages are emitted at INFO level; done means they no longer obscure useful INFO logs while remaining available at a lower log level.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100