rust-lang / rust-lang/rust-analyzer
Show progress when waiting for file lock on package cache
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Usually when I open a file in my editor, rust-analyzer quickly reports progress (scanning, downloading dependencies, etc).
However, if another process is holding a lock on the package cache, rust-analyzer provides not feedback, and it is unclear what is going on when looking at my editor. I tend to think "Is it done analyzing? Why am I not seeing feedback? Is something broken?".
It would be useful if the LSP would indicate that it is waiting for a lock on the package cache, in the same way it indicates when it is indexing, fetching dependencies, etc.
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
Start by tracing rust-analyzer's existing LSP progress reporting for indexing and dependency fetching, then locate the package-cache lock wait. Done means the editor receives a clear progress indication while that lock is held; the issue names no specific files or tests, so identify the relevant code and test entry points first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100