rust-lang / rust-lang/rust-analyzer
`rust-analyzer` stuck on “Getting code actions from 'rust-analyzer' (configure)” in VSCode when working in biome repo
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Type: Bug
- Clone the repo:
git clone https://github.com/biomejs/biome
-
Open the project in VSCode with the
rust-analyzerextension installed. -
Create, edit and save a new source file in a directory like
crates/biome_js_analyze/src/lint/nursery/.
Extension version: 0.3.2593
VS Code version: Code 1.104.1 (0f0d87fa9e96c856c5212fc86db137ac0d783365, 2025-09-17T23:36:24.973Z)
OS version: Linux x64 6.14.0-29-generic
Modes:
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (8 x 4500) |
| GPU Status | 2d_canvas: enabled direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off trees_in_viz: disabled_off video_decode: enabled video_encode: disabled_software vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: disabled_off webnn: disabled_off |
| Load (avg) | 2, 2, 2 |
| Memory (System) | 31.28GB (15.48GB free) |
| Process Argv | python-project-prices-options/ --crash-reporter-id 9746525a-a815-4ecc-8c8a-eb4404b733be |
| Screen Reader | no |
| VM | 0% |
| DESKTOP_SESSION | ubuntu |
| XDG_CURRENT_DESKTOP | Unity |
| XDG_SESSION_DESKTOP | ubuntu |
| XDG_SESSION_TYPE | x11 |
A/B Experiments
vsliv368cf:30146710
binariesv615:30325510
vscrp:30673768
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
996jf627:31283433
pythonrdcb7:31342333
usemplatestapi:31297334
aj953862:31281341
nesew2to5:31336538
agentgpt4:31387437
82j33506:31327384
nes-set-on:31340697
63221493:31336333
envsactivate1:31353494
0927b901:31350571
ovsp_t:31383296
aa_t:31379598
0cj2b977:31352657
gendocstringf:31387973
0574c672:31362109
cloudbuttont:31379625
todos-1:31384886
treatment_gpt5applypatchexclusively:31387917
42190218_ostrepl:31382710
metis-embeddings:31388492
trigger-command-fix:31379601
auto_model_enabled:31385282
copilot-gpt-5-mini:31386632
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 by opening the biome repository in VS Code, editing a file under crates/biome_js_analyze/src/lint/nursery/, and saving it. Start by inspecting rust-analyzer and VS Code logs for the code-actions request; done means the configure code-actions request completes instead of remaining stuck.
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