rust-lang / rust-lang/rust-analyzer
Opening a rust file in the tests directory of the rust-lang/rust workspace triggers overly long loop turn
Open
Nobody has claimed this yet.
C-bug
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Basically opening any file in that directory has a high change for me to trigger it on the textDocument/didOpen notification for me which seems odd as it doesn't matter how big the file in question is ... So something odd is going on here
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 reproducing the issue by opening a Rust file in the tests directory of the rust-lang/rust workspace and observing the textDocument/didOpen notification. Trace the overly long loop turn to determine why it occurs regardless of file size; done means the trigger is understood and the regression is fixed without affecting normal file opening.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100