-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rust-analyzer on WSL cannot find sysroot, VSCode 1.49.2 #6106
Comments
Is it possible that |
Is there some way besides that which VSCode might require for the path to be recognized? |
You are printing the PATH for your shell. This is not necessarily identical to the PATH for graphical applications. For example |
Yes, I always run |
Though in any case, I see in
|
If there are any additional diagnostics I can enable to help debug this please let me know :) |
Have no idea what's going on here. Added some more logging in #6230. |
@ChronosWS are you still seeing this? |
I experienced a similar issue. If I open an individual Rust file in VSCode (i.e. |
@patbecich r-a requires the cargo workspace to be fully opened for it to work, single files do not work properly(we have some stuff now that allows them to work in some fashion but very very limited). Closing as OP hasn't replied and doesn't seem to be active currently anymore. |
VSCode: 1.49.2
Rust-Analyzer plugin: 0.2.328
Expected: Language server loads and operates correctly (as it did yesterday before today's VSCode update)
Actual: Language server fails to load, all language features unavailable in VSCode
Error (from extension toast):
Diagnostics:
From the VSCode Bash shell:
From Rust Analyzer Language Server diagnostics window:
From Rust Analyzer Client diagnostics window:
The text was updated successfully, but these errors were encountered: