"failed fetching toolchain version" in VScode, with Mise #19830
-
So, I've got Rust 1.87 installed via rustup (… via mise, although in this case, I don't think that's as relevant as it would normally be; recent versions of mise "just" invoke rustup, and Rust appears to be installed in the normal location.) The statusbar in VScode is reporting "Failed to load workspaces."; and the output pane reports:
It gets stranger, though, if I explicitly set the "rust-analyzer.server.extraEnv": { "PATH": "/Users/ec/.cargo/bin:$PATH" }, … because the error-messages now include an explicit path that produces the same error-message:
If I open a terminal with no environment with $ env - dash
$ env
PWD=/Users/ec
$ cd "/Users/ec/Sync/Code/twag" && "/Users/ec/.cargo/bin/cargo" "--version"
cargo 1.87.0 (99624be96 2025-05-06) How have I screwed up my VScode /
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
… restarting VScode fully fixed the problem. Not restarting the LSP server; not reloading extensions (my usual go-tos), but quitting the (macOS) program entirely, closing all of the half-dozen long-lived workspaces on my machine. How strange. I've never had to do that intentionally before. |
Beta Was this translation helpful? Give feedback.
… restarting VScode fully fixed the problem. Not restarting the LSP server; not reloading extensions (my usual go-tos), but quitting the (macOS) program entirely, closing all of the half-dozen long-lived workspaces on my machine.
How strange. I've never had to do that intentionally before.