Rust-analyzer in vs-code is failing to fetch "cargo metadata" #14387
Replies: 1 comment 4 replies
-
|
What is the content of |
Beta Was this translation helpful? Give feedback.
-
|
@bjorn3 Attached is the screen shot of the config file |
Beta Was this translation helpful? Give feedback.
-
|
That should be fine. Can you try running |
Beta Was this translation helpful? Give feedback.
-
|
That command ran successfully from terminal and the output is a large set of data |
Beta Was this translation helpful? Give feedback.
-
|
The root cause for my issue was some default buildvm script in the ~/.profile that hogs the session/terminal start for 60s. This is causing buildenvironment related issues in the vs-code extension host. Disabling the script fixed things for me. The error logs look like below |
Beta Was this translation helpful? Give feedback.
-
Hi,
I am new to rust and still figuring out how things work. I am trying to setup rust dev environment using vs-code and rust-analyzer extension.
In my dev environment I can't access public crates.io and has a config file defined with "crates-io-mirror" (proxy registry) as a replacement for the "crates.io" Config file also includes the registry index and token.
Cargo tool from terminal works fine, but for some reason the rust-analyzer extension in the vs-code is failing. Any kind of debugging pointers are appreciated?? like how to run the rust-analyzer binary from terminal?? any specific debug arguments to pass etc.,
Error log
Beta Was this translation helpful? Give feedback.
All reactions