-
Notifications
You must be signed in to change notification settings - Fork 165
RLS doesn't support RUSTC_WRAPPER
s
#460
Comments
This error persists in 0.5.1, which completely breaks the extension. |
I’m facing this issue too. As a temporary workaround, you can run in a terminal:
Wait for the build to terminate, then hit |
For me the error was gone after updating to 0.5.2 |
I’m still facing the issue with rls-vscode 0.5.3. |
I got it fixed by disabling |
I just updated to VSCode 1.30.1. After that, I uninstalled the rust extension, reloaded VSCode, then reinstalled the rust extension and the errors went away for me. 2019-01-01Well...the issue is back again... |
I'm on Windows 10, VS Code 1.30.2, Running Not sure if this will work for everyone, but I was able to fix this issue by doing a complete removal of all rust toolchains, rustup, and deleting and leftovers (e.g. Edit: Tried this on macOS (but otherwise same versions of everything else) and am still running into the same issue there... I can't think of any specific reason why macOS would be different here... Edit 2: It seems using |
Just to confirm that |
RUSTC_WRAPPER
s
I get the same outcome with a slightly different error message in
Any news on this bug? The problem only seems to happen on mine when I add |
More details:
|
Bizarrely, when I change the |
The only thing that this extension seems to do is show an single error that covers every line in my Cargo.toml that says "Could not compile ". The crate changes every time I restart VS Code, but the problem stays the same.
The problems panel shows this:
Running that command manually reports
This seems to me that I have a version incompatibility between RLS and rls-vscode. I've updated both (and VS Code itself). The command
rls --version
reportsrls-preview 1.31.6 (daa138c 2018-11-20)
. I have version 0.4.10 of rls-vscode.It would be nice to fix this problem, and also to be able to detect such version incompatibilities in the future.
The text was updated successfully, but these errors were encountered: