rust-analyzer failed to load workspace #4172

Redoubts · 2020-04-27T15:05:13Z

I installed rust with brew on MacOS, and I'm noticing this error on a hello world project with VS Code:

rust-analyzer failed to load workspace: 
    Failed to find sysroot for Cargo.toml file ./rust_new/Cargo.toml. 
    Is rust-src installed?: rustup component add rust-src failed

I didn't install with rustup, and I figured I wouldn't need to. This suggests I must, but why? Does this suggest I need the complier source to use your package in my editor?

The text was updated successfully, but these errors were encountered:

lnicola · 2020-04-27T15:07:58Z

rust-src is the standard library, not compiler source code. rust-analyzer needs it to know what the standard library types are.

Redoubts · 2020-04-27T15:13:05Z

Isn't that rust-std? Rust's homepage describes rust-src as the Rust source code.

https://github.com/rust-lang/rustup#can-rustup-download-the-rust-source-code

bjorn3 · 2020-04-27T16:29:39Z

rust-src is the source code of the standard library. rust-std is the compiled version of the standard library.

zdcthomas · 2020-04-27T17:49:56Z

Hey,
I just upgraded to the newest rust-analyzer version, and I've just started having the same issue.

I'm using nvim with coc-rust-analyzer
I've run rustup update
Ive run rustup comonent add rust-src
the only thing left that I can think of doing is setting RUST_SRC_PATH but I'm not sure what to set that to/why I only now have to set it.

bjorn3 · 2020-04-27T17:56:45Z

What is the output of ls $(rustc --print sysroot)/lib/rustlib/src/rust/src? For me it is:

build_helper  libcore         libpanic_unwind  libprofiler_builtins  librustc_asan  librustc_msan  libstd     libterm  libunwind  tools
liballoc      libpanic_abort  libproc_macro    librustc              librustc_lsan  librustc_tsan  libsyntax  libtest  stdarch

zdcthomas · 2020-04-27T19:33:36Z

it seems like I only have the path up to lib/rustlib I don't have src/rust/src, should I reinstall stuff? What I have in rustlib is

components                              manifest-rustc
etc                                     rust-installer-version
manifest-rust-docs                      x86_64-apple-darwin
manifest-rust-std-x86_64-apple-darwin

zdcthomas · 2020-04-28T00:59:33Z

Quick update, I uninstalled all of the rust toolchain, and then reinstalled and the issue has gone away

matklad · 2020-04-29T07:50:17Z

Closing the issue, as it seems to be the problem with local toolchain installation. it would be awesome if we could diagnose and warn about this on our side, but I doubt we can provide info more useful then the existing error message.

woelper · 2020-09-06T05:47:50Z

I have the same issue with nightly-x86_64-unknown-linux-gnu (1.48.0-nightly) on ubintu linux and vs code. I have completely uninstalled rust and reinstalled, but I get

rust-analyzer failed to load workspace: Failed to find sysroot for Cargo.toml file /mnt/md2/woelper/dircpy/Cargo.toml.
Is rust-src installed?:
can't load standard library from sysroot /home/woelper/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src (discovered via `rustc --print sysroot`)
try running `rustup component add rust-src` or set `RUST_SRC_PATH`

running rustup component add rust-src yields info: component 'rust-src' is up to date.

it looks like I am missing the src folder: ls /home/woelper/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust shows just Cargo.lock library.

$(rustc --print sysroot) points to /home/woelper/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu, which does exist.

I should add that this is a VS code remote session, maybe this complicates things?

bjorn3 · 2020-09-06T07:08:28Z

Try rustup component add rust-src --toolchain nightly.

woelper · 2020-09-06T08:16:58Z

rustup component add rust-src --toolchain nightly

Thanks for your reply, this produces the following result:

rustup component add rust-src --toolchain nightly
info: component 'rust-src' is up to date

woelper · 2020-09-08T09:24:48Z

I am able to reproduce this with Mac OS 10.15.6 and 1.48.0-nightly as well:

rust-analyzer failed to load workspace:
Failed to find sysroot for Cargo.toml file /Users/woelper/catapult-imgui/Cargo.toml. Is rust-src installed?
Caused by: can't load standard library from sysroot /Users/woelper/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/src/rust/src (discovered via `rustc --print sysroot`) try running `rustup component add rust-src` or set `RUST_SRC_PATH`

I also ran rustup component add rust-src --toolchain nightly, which caused info: component 'rust-src' is up to date

jondot · 2020-09-11T14:23:29Z

rust-src changed the path layout, which is the source of the problem.

September:

August:

jondot · 2020-09-11T14:45:06Z

Lastly, this should be fixed if you take recent version from master:
6b8bc13#diff-30888fefce138d15c65ceb40b37b7ad2R146

lnicola · 2020-09-12T03:41:12Z

This should have been fixed in #5586.

jondot · 2020-09-12T11:32:27Z

Thanks @lnicola I feel that maybe the official extension isn't picking up that change yet, which causes the breakage, even though everything should work by now. That's why I build and install from source.

granddaifuku · 2020-09-13T02:33:05Z

I still have the same issue with MacOS 10.15.6, 1.48.0-nightly even I build and install from source.

There's only Cargo.lock, library
Here's what I got.

$ cd $(rustc --print sysroot)/lib/rustlib/src/rust
$ ls
Cargo.lock	library
$ rustup component add rust-src --toolchain nightly
info: component 'rust-src' is up to date

jondot · 2020-09-13T08:42:56Z

I believe at this stage its just a matter of verifying that you actually use rust-analyzer from source (first uninstall from your VSCode, then install)

granddaifuku · 2020-09-13T10:33:47Z

My rust environment is not working, so I decided to uninstall and reinstall entire rust system.
However I still struggling with this issue.

Emacs version 27.1(9.0)

Here's what I did.

~ % curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh 
~ % rustup install nightly
~ %  rustup default nightly
~ % git clone https://github.com/rust-analyzer/rust-analyzer.git && cd rust-analyzer
rust-analyzer % cargo xtask install --server
~ % rustup component add rust-src

Emacs lsp says

LSP :: Connected to [rust-analyzer:94373 status:starting]. [2 times]
LSP :: rust-analyzer:94373 initialized successfully
LSP :: rust-analyzer failed to load workspace: Failed to find sysroot for Cargo.toml file /Users/yufuku/Develop/Rust/hello/Cargo.toml. Is rust-src installed?: could not find libcore in sysroot path `/Users/yufuku/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/src/rust/library/std/src`
LSP :: Error from the Language Server: Rust Analyzer is still loading... (Unknown error) [4 times]

$(rustc --print sysroot)/lib/rustlib/src/rust  % ls
Cargo.lock	library

There's no src directory.

rsignavong · 2020-09-16T20:16:34Z

It's not working for me too.
The latest release 0d03fe6 is trying to load libcore from rust-src/src from rustc stable version but it doesn't read the rust-src/library folder in rustcnightly version

avocade · 2020-10-08T11:12:36Z

Just running rustup component add rust-src worked fine for me with latest macOS catalina.

luiswirth · 2020-10-09T15:05:49Z

I'm having the same problem too on Arch Linux. Maybe the rust-src path changes ever so often?

I think the path for me is $(rustc --print sysroot)/lib/rustlib/src/rust/library/std/src or is this something else?

lnicola · 2020-10-09T15:19:52Z

@LU15W1R7H the path changed only once (recently), and while rust-analyzer supports both locations, for that to work you must unset RUST_SRC_PATH. See the discussion in #6178.

stardiviner · 2020-10-30T02:15:10Z

I got same problem on Arch Linux.

Here is the error log in Emacs buffer *rust-analyzer::stderr*:

[ERROR rust_analyzer::reload] failed to load workspace: Failed to find sysroot for Cargo.toml file /home/stardiviner/Documents/learning/Rust/hello/Cargo.toml. Is rust-src installed?: could not find libcore in sysroot path `/home/stardiviner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src`

I create a test project using command cargo new hello-world.

Did uninstall & reinstall nightly toolchain, and here is the output of command:

$ ls $(rustc --print sysroot)/lib/rustlib/src/rust/src

llvm-project

And I execute command:

$ rustup update && rustup component add rust-src

info: syncing channel updates for 'nightly-x86_64-unknown-linux-gnu'
info: latest update on 2020-10-30, rust version 1.49.0-nightly (6bdae9edd 2020-10-29)
info: skipping nightly which is missing installed components 'rls-preview', 'rustfmt-preview'
info: syncing channel updates for 'nightly-2020-10-29-x86_64-unknown-linux-gnu'
info: latest update on 2020-10-29, rust version 1.49.0-nightly (31ee872db 2020-10-28)
info: skipping nightly which is missing installed components 'rls-preview', 'rustfmt-preview'
info: syncing channel updates for 'nightly-2020-10-28-x86_64-unknown-linux-gnu'
info: latest update on 2020-10-28, rust version 1.49.0-nightly (07e968b64 2020-10-27)
info: skipping nightly which is missing installed components 'rls-preview', 'rustfmt-preview'
info: syncing channel updates for 'nightly-2020-10-27-x86_64-unknown-linux-gnu'
info: latest update on 2020-10-27, rust version 1.49.0-nightly (fd542592f 2020-10-26)
info: skipping nightly which is missing installed components 'rls-preview', 'rustfmt-preview'
info: syncing channel updates for 'nightly-2020-10-26-x86_64-unknown-linux-gnu'
info: latest update on 2020-10-26, rust version 1.49.0-nightly (4760b8fb8 2020-10-25)
info: skipping nightly which is missing installed components 'rls-preview', 'rustfmt-preview'
info: syncing channel updates for 'nightly-2020-10-25-x86_64-unknown-linux-gnu'

  nightly-x86_64-unknown-linux-gnu unchanged - rustc 1.49.0-nightly (ffa2e7ae8 2020-10-24)

info: cleaning up downloads & tmp directories
info: component 'rust-src' is up to date

I have following setting in ~/.zshrc:

export RUST_SRC_PATH="$(rustc --print sysroot)/lib/rustlib/src/rust/src"

lnicola · 2020-10-30T06:18:07Z

@stardiviner try to unset RUST_SRC_PATH and check what which rust-analyzer prints.

stardiviner · 2020-10-30T07:39:02Z

@lnicola After unset RUST_SRC_PATH, The command which rust-analyzer points to /usr/bin/rust-analyzer.
It seems from my Arch Linux installed package rust-analyzer.

lnicola · 2020-10-30T07:42:10Z

That's strange, recent versions print a "RUST_SRC_PATH might be incorrect, try unsetting it" message if the variable is set.

Anyway, is it working now? I think RUST_SRC_PATH should point to the sysroot, not to the source code directory, but it generally works without the variable.

stardiviner · 2020-10-30T07:46:56Z

Still not work.
Same error:

[ERROR rust_analyzer::reload] failed to load workspace: Failed to find sysroot for Cargo.toml file /home/stardiviner/Documents/learning/Rust/hello/Cargo.toml. Is rust-src installed?: could not find libcore in sysroot path `/home/stardiviner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src`

I'm sure I installed rust-src component. But why I don't have libcore in sysroot path? I checked the upper path. I found I only have llvm-project directory. Is this correct and normal?

kushaldas · 2020-11-14T06:34:21Z

I don't have RUST_SRC_PATH set, tried to use both auto downloaded via coc-rust-analyzer, and local build:

rust-analyzer e8c8039

Same error.

stardiviner · 2020-11-14T09:08:04Z

@kushaldas Can you provide more info about your system and editor etc? and try to get env variable info from editor.

flodiebold · 2020-11-14T13:03:34Z

Edit: I've encountered some peculiar behavior of Emacs with regards to this env variable. While RUST_SRC_PATH is not set anywhere in the system environment, emacs has this variable set for some odd reason (I can echo it in the M-x shell, nowhere else).

If you're using Spacemacs, it has this thing where it saves the environment in a file and reproduces it from there (see ~/.spacemacs.env). Or if you're not, maybe there's something similar going on. We're ignoring RUST_SRC_PATH now if it doesn't contain core though, so it shouldn't matter much anymore.

Same error.

Please post the exact error message you're getting, and the output from rustc --print sysroot in your project directory.

kushaldas · 2020-11-14T13:47:50Z

@kushaldas Can you provide more info about your system and editor etc? and try to get env variable info from editor.

I am using neovim and coc-rust-analyzer. After fighting for the whole day, I removed all rust* from the system, and did a fresh install. Now everything is again working. Thank you for the help.

uWynell · 2020-11-19T14:54:55Z

@kushaldas Can you provide more info about your system and editor etc? and try to get env variable info from editor.

I am using neovim and coc-rust-analyzer. After fighting for the whole day, I removed all rust* from the system, and did a fresh install. Now everything is again working. Thank you for the help.

How did you install rust? I'm just experiencing the same issue now

IgnisDa · 2021-06-18T03:04:55Z

I encountered this problem when using rust in a custom alpine docker image. The following solved it.

RUN sudo apk del cargo rust
RUN curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y

soraiemame · 2022-01-09T05:42:12Z

I want to use rustc 1.42.0 and I am getting the same error. I installed rust with rustup on Windows10.

rust-toolchain

1.42.0-x86_64-pc-windows-gnu

$ rustup toolchain list

stable-x86_64-pc-windows-gnu (default)
nightly-x86_64-pc-windows-gnu
1.42.0-x86_64-pc-windows-gnu (override)

rust-analyzer v0.2.853

I have tried

$ rustup component add --toolchain 1.42.0-x86_64-pc-windows-gnu rust-src
$ rustup component add rust-src

but rust-analyzer shows me the same error.

lnicola · 2022-01-09T15:19:18Z

@soraiemame the sysroot (rust-src) structure changed in 1.47 and we only support that and newer versions.

soraiemame · 2022-01-10T03:55:30Z

Thank you for responding. I did not know that. I will use the stable toolchain for now then.

hom · 2022-03-23T05:16:49Z

In Windows system I try to install below and resolved:

scoop install rustup

Integralist · 2022-04-11T19:59:48Z

For anyone jumping to the end of this thread, the solution for me (mentioned here) was:

export RUST_SRC_PATH="$(rustc --print sysroot)/lib/rustlib/src/rust/src"

pluveto · 2022-04-15T11:09:00Z

export RUST_SRC_PATH="$(rustc --print sysroot)/lib/rustlib/src/rust/src"

for /etc/profile or ~/.zshrc or ~/.bashrc not working for me.

ls $(rustc --print sysroot)/lib/rustlib/src/rust/src
build_helper libpanic_abort libprofiler_builtins libtest tools
liballoc libpanic_unwind libstd libunwind
libcore libproc_macro libterm stdarch

HoikanChan · 2022-04-30T14:52:37Z

Same issues, just run rustup update, fixed it

lnicola · 2022-04-30T16:11:41Z

@pluveto which Rust version are you on?

pluveto · 2022-05-01T06:04:05Z

@pluveto which Rust version are you on?

latest nightly when I post. finally I reinstalled my os and fixed it. this may be a issue with some other software

Dequog · 2022-07-25T17:51:45Z

After trying various things up above, I uninstalled and reinstalled vscode which fixed the problem for me.

Jeklah · 2022-07-26T19:35:46Z

I ran into this problem installing rust_analyser.
I installed rustup, used that to install stable toolchain.
Ran rustup which rustc which showed a different version to what rustc -V showed.
Ran apt-get remove rustc to remove invalid install.
Checked with running rustc -V again, which now matched rustup.

After that, the rust_analyser error disappeared and clippy kicked into action.

BruceGuanFF · 2022-10-09T07:04:40Z

Hey, I just upgraded to the newest rust-analyzer version, and I've just started having the same issue.

I'm using nvim with coc-rust-analyzer

I've run rustup update

Ive run rustup comonent add rust-src
the only thing left that I can think of doing is setting RUST_SRC_PATH but I'm not sure what to set that to/why I only now have to set it.

it works after running rustup component add rust-src

ffanyq · 2022-10-09T10:09:49Z

I have sloved this problem after I copy the folder
".\nightly-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library" to the
".\nightly-2020-05-10-x86_64-pc-windows-msvc\lib\rustlib\src\rust"

(nightly-x86_64-pc-windows-msvc and nightly-2020-05-10-x86_64-pc-windows-msvc both are in the sysroot folder).

The reason of the problem is the version error of rustup, as above, it can't identified the old version toolchains' folder path layout.

whu-geocat · 2022-11-09T06:54:20Z

I have the same issue with nightly-x86_64-unknown-linux-gnu (1.48.0-nightly) on ubintu linux and vs code. I have completely uninstalled rust and reinstalled, but I get
rust-analyzer failed to load workspace: Failed to find sysroot for Cargo.toml file /mnt/md2/woelper/dircpy/Cargo.toml.
Is rust-src installed?:
can't load standard library from sysroot /home/woelper/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src (discovered via `rustc --print sysroot`)
try running `rustup component add rust-src` or set `RUST_SRC_PATH`
running rustup component add rust-src yields info: component 'rust-src' is up to date.

it looks like I am missing the src folder: ls /home/woelper/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust shows just Cargo.lock library.

$(rustc --print sysroot) points to /home/woelper/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu, which does exist.

I should add that this is a VS code remote session, maybe this complicates things?

+1

fritzrehde · 2022-12-03T16:02:42Z

I had this problem on Arch Linux too, and solved it with sudo pacman -R rust. So, for some reason unknown to me, rust was installed by the systems package manager and rustup, so deleting the version installed by pacman has solved my problems.

keks · 2022-12-19T13:19:02Z

On manjaro linux I was able to resolve this by using the vscodium-bin package from AUR instead of the code package from community.

Jayuda · 2023-01-08T13:24:49Z

I had this problem on Arch Linux too, and solved it with sudo pacman -R rust. So, for some reason unknown to me, rust was installed by the systems package manager and rustup, so deleting the version installed by pacman has solved my problems.

Yes its work like a charm.

AndhikaWB · 2023-08-03T17:15:33Z

This is a bit off-topic but in case you're using offline installer where rustup is not available, you can download rust-src directly using this URL format: https://static.rust-lang.org/dist/YYYY-MM-DD/rust-src-X.X.X.tar.gz.

Check release date and version from this page (latest release only). Example link for v1.71.0: https://static.rust-lang.org/dist/2023-07-13/rust-src-1.71.0.tar.gz.

EDIT: Can also be seen here. Download the toml file that you want and search for "rust-src.target"

EugeneChung · 2023-12-10T04:11:06Z

rustup component add rust-src doesn't work for me, neither.
As @AndhikaWB mentioned, I manually set up rust-src from https://static.rust-lang.org/dist/2023-12-07/rust-src-1.74.1.tar.gz.

lpnh · 2023-12-13T22:46:50Z

I had this problem on Arch Linux too, and solved it with sudo pacman -R rust. So, for some reason unknown to me, rust was installed by the systems package manager and rustup, so deleting the version installed by pacman has solved my problems.

For anyone who might be experiencing "the workspace is missing a sysroot" issue, the solution mentioned above worked perfectly.

matklad closed this as completed Apr 29, 2020

rsignavong mentioned this issue Sep 16, 2020

rust-analyzer failed to load workspace again #6020

Closed

kidonng mentioned this issue Dec 6, 2020

rust: add rust-src Homebrew/homebrew-core#66315

Closed

5 tasks

Kreyren mentioned this issue Aug 16, 2021

Missing rust-src which is causing rust-analyzer to fatal in vscodium mozilla/nixpkgs-mozilla#263

Open

NireBryce mentioned this issue Apr 10, 2024

I think this solves the rust-analyzer problem LibArticles/articleman#20

Closed

NewUserHa mentioned this issue Jan 29, 2025

offline installer should include rust-src rust-lang/rust#136268

Open

rust-analyzer failed to load workspace #4172

rust-analyzer failed to load workspace #4172

Comments

Redoubts commented Apr 27, 2020

lnicola commented Apr 27, 2020

Redoubts commented Apr 27, 2020

bjorn3 commented Apr 27, 2020

zdcthomas commented Apr 27, 2020

bjorn3 commented Apr 27, 2020 • edited Loading

zdcthomas commented Apr 27, 2020

zdcthomas commented Apr 28, 2020

matklad commented Apr 29, 2020

woelper commented Sep 6, 2020 • edited Loading

bjorn3 commented Sep 6, 2020

woelper commented Sep 6, 2020 • edited Loading

woelper commented Sep 8, 2020 • edited Loading

jondot commented Sep 11, 2020

jondot commented Sep 11, 2020

lnicola commented Sep 12, 2020

jondot commented Sep 12, 2020

granddaifuku commented Sep 13, 2020

jondot commented Sep 13, 2020

granddaifuku commented Sep 13, 2020

rsignavong commented Sep 16, 2020 • edited Loading

avocade commented Oct 8, 2020

luiswirth commented Oct 9, 2020 • edited Loading

lnicola commented Oct 9, 2020

stardiviner commented Oct 30, 2020 • edited Loading

lnicola commented Oct 30, 2020

stardiviner commented Oct 30, 2020 • edited Loading

lnicola commented Oct 30, 2020 • edited Loading

stardiviner commented Oct 30, 2020

kushaldas commented Nov 14, 2020

stardiviner commented Nov 14, 2020

flodiebold commented Nov 14, 2020

kushaldas commented Nov 14, 2020 • edited Loading

uWynell commented Nov 19, 2020 • edited Loading

IgnisDa commented Jun 18, 2021

soraiemame commented Jan 9, 2022

lnicola commented Jan 9, 2022

soraiemame commented Jan 10, 2022

hom commented Mar 23, 2022

Integralist commented Apr 11, 2022

pluveto commented Apr 15, 2022

HoikanChan commented Apr 30, 2022

lnicola commented Apr 30, 2022

pluveto commented May 1, 2022 • edited Loading

Dequog commented Jul 25, 2022

Jeklah commented Jul 26, 2022

BruceGuanFF commented Oct 9, 2022

ffanyq commented Oct 9, 2022 • edited Loading

whu-geocat commented Nov 9, 2022

fritzrehde commented Dec 3, 2022

keks commented Dec 19, 2022

Jayuda commented Jan 8, 2023

AndhikaWB commented Aug 3, 2023 • edited Loading

EugeneChung commented Dec 10, 2023

lpnh commented Dec 13, 2023

bjorn3 commented Apr 27, 2020 •

edited

Loading

woelper commented Sep 6, 2020 •

edited

Loading

woelper commented Sep 6, 2020 •

edited

Loading

woelper commented Sep 8, 2020 •

edited

Loading

rsignavong commented Sep 16, 2020 •

edited

Loading

luiswirth commented Oct 9, 2020 •

edited

Loading

stardiviner commented Oct 30, 2020 •

edited

Loading

stardiviner commented Oct 30, 2020 •

edited

Loading

lnicola commented Oct 30, 2020 •

edited

Loading

kushaldas commented Nov 14, 2020 •

edited

Loading

uWynell commented Nov 19, 2020 •

edited

Loading

pluveto commented May 1, 2022 •

edited

Loading

ffanyq commented Oct 9, 2022 •

edited

Loading

AndhikaWB commented Aug 3, 2023 •

edited

Loading