rust-lang / rust-lang/rust-analyzer
Extract module to file broken in WSL/Remote
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Hi :)
It seems that the "extract module to file "quick action relies on some path semantics from VSCode that are not consistently applied when not working locally.
The stacktrace is fairly straightforward:
NOTE: I've replaced the Linux local path with <path>
cannot open vscode-remote://wsl%2Bubuntu-18.04/<path> Detail: Unable to read file 'vscode-remote://wsl+ubuntu-18.04/<path>' (Error: Unable to resolve non-existing file 'vscode-remote://wsl+ubuntu-18.04/<path>')
This may be somewhat related to #7208, but the root cause is perhaps a little different.
Thanks!
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 "extract module to file" quick action in a WSL or Remote VS Code session and trace the path handling that produces the reported vscode-remote URI. Done means the action can create or open the extracted module without the non-existing-file resolution error.
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
- Mostly clear
- Newbie friendliness
- 30/100