rust-lang / rust-lang/rust-analyzer
errors don't show in the vscode Problems section when Warnings and Infos are excluded in filters
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Currently, I have a lot of warnings about unused items and other things in my new project, which I don't care about at this point. I don't want to see over 100 warnings in the Problems area; I oniy want to see errors. So, I disable warnings and infos in the filters for Problems. Then, often the errors aren't displayed in Problems unless I:
- toggle to another tab in the bottom panel and back again (e.g. Problems -> Output -> Problems); or
- enable warnings and infos in the filter, then disable them again.
I have to do this after every time I save the file, which I do frequently to refresh the errors, as I am fixing multiple errors.
Expected behavior: The Problems filters are respected and errors are correctly displayed whenever enabled in the filters.
I am referring to this Problems tab in the bottom panel:

rust-analyzer version: 0.3.1301-standalone
rustc version: 1.64.0 (a55dd71d5 2022-09-19)
relevant settings: (eg. client settings, or environment variables like CARGO, RUSTUP_HOME or CARGO_HOME)
vscode info:
Version: 1.73.0
Commit: 8fa188b2b301d36553cbc9ce1b0a146ccb93351f
Date: 2022-11-03T14:04:08.642Z
Electron: 19.1.4
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Linux x64 6.0.8-1-MANJARO
Sandboxed: No
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 issue in VS Code with rust-analyzer by disabling warnings and infos in the Problems filters, then saving a file with errors. Trace the diagnostic refresh and Problems filtering behavior; done means enabled errors remain visible after each save without toggling tabs or filters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, vscode
- Domain
- developer-experience, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100