Skip to content

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

Closed
ilmai opened this issue Apr 23, 2024 · 10 comments
Closed

VSCode extension fails to run checks #17127

ilmai opened this issue Apr 23, 2024 · 10 comments
Labels
C-bug Category: bug

Comments

@ilmai
Copy link

ilmai commented Apr 23, 2024

Latest version fails to run checks with the following error in logs (paths censored):

Caused by:
  process didn't exit successfully: `/home/***/.vscode-server/extensions/rust-lang.rust-analyzer-0.3.1932-linux-x64/server/rust-analyzer /home/***/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/clippy-driver /home/***/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc - --crate-name ___ --print=file-names --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=split-debuginfo --print=crate-name --print=cfg` (exit status: 1)
  --- stderr
  error: Unrecognized option: 'keep-going'

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

@ilmai ilmai added the C-bug Category: bug label Apr 23, 2024
@lnicola
Copy link
Member

lnicola commented Apr 23, 2024

Do you have a rust-toolchain file and does cargo check --keep-going work?

@ilmai
Copy link
Author

ilmai commented Apr 23, 2024

I don't. cargo check --keep-going works normally in the terminal.

@Veykril
Copy link
Member

Veykril commented Apr 23, 2024

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

@ilmai
Copy link
Author

ilmai commented Apr 23, 2024

Windows:
stable-x86_64-pc-windows-msvc (default)
beta-x86_64-pc-windows-msvc
nightly-x86_64-pc-windows-msvc

WSL:
stable-x86_64-unknown-linux-gnu (default)

@Veykril
Copy link
Member

Veykril commented Apr 23, 2024

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

@ilmai
Copy link
Author

ilmai commented Apr 23, 2024

Both are 1.77.2

bors added a commit that referenced this issue Apr 26, 2024
internal: Show workspace info in the status bar

cc #17127
RalfJung pushed a commit to RalfJung/rust that referenced this issue Apr 26, 2024
RalfJung pushed a commit to RalfJung/rust that referenced this issue Apr 27, 2024
@IWANABETHATGUY
Copy link

As a workaround, you could downloaded the latest rust-analyzer https://github.com/rust-lang/rust-analyzer/releases/tag/2024-04-22, and override the old one,

@ilmai
Copy link
Author

ilmai commented May 6, 2024

Just tried the latest version, 0.3.1950. I still have the same issue but I noticed new information has been added to the popup:
image

@jeiroa
Copy link

jeiroa commented May 10, 2024

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:
snapshot

rust-analyzer version: 0.3.1950
rustc version: 1.78.0
editor or extension: VSCode 1.89.1
OS: Ubuntu 22.04 LTS (Linux x64 5.15.0-106 generic)

@ilmai
Copy link
Author

ilmai commented May 28, 2024

I updated to the latest version yesterday and this seems to be fixed

@ilmai ilmai closed this as completed May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: bug
Projects
None yet
Development

No branches or pull requests

5 participants