-
Notifications
You must be signed in to change notification settings - Fork 1.8k
VSCode extension fails to run checks #17127
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
Comments
Do you have a |
I don't. |
What toolchain versions do you have installed in WSL, what toolchain versions do you have installed locally? Looks like r-a is picking the wrong one somehow |
Windows: WSL: |
is your windows stable version older? (I just wanna check what toolchain r-a might try to be running on, we should really make it print that somewhere). I assume our toolchain selection somehow makes it use your windows toolchain instead of the WSL one |
Both are 1.77.2 |
internal: Show workspace info in the status bar cc #17127
internal: Show workspace info in the status bar cc rust-lang/rust-analyzer#17127
internal: Show workspace info in the status bar cc rust-lang/rust-analyzer#17127
As a workaround, you could downloaded the latest |
I have the same issue @ilmai commented above. I noticed it is happening since the previous version of rust-analyzer. Attached you can see the same error message when I hover over rust-analyzer tab at the bottom of VSCode IDE: rust-analyzer version: 0.3.1950 |
I updated to the latest version yesterday and this seems to be fixed |
Latest version fails to run checks with the following error in logs (paths censored):
This error was from WSL but a similar error is produced on Windows and Mac. The error is fixed by installing the previous version 0.3.1924. This happens on all projects I tested with, regardless of if they have a build script or not.
rust-analyzer version: 0.3.1932
rustc version: 1.77.2
editor or extension: VSCode
The text was updated successfully, but these errors were encountered: