Stuck at 'rust_analyzer: -32801: waiting for cargo metadata or cargo check'

[luisvgs]

I'm opening a project directory and rust-analyzer seems to be stuck at loading. I checked if perhaps was a project issue but the error persists in both big (5+ dependencies) and small projects (using 1 dependency). I'm using neovim v0.7.0-dev in Ubuntu. Any suggestion of how to solve this issue? Thanks in advance.

rust-analyzer version: (eg. output of "Rust Analyzer: Show RA Version" command)
rust-analyzer d9b2291 2021-11-29 stable

rustc version: (eg. output of rustc -V)
rustc 1.56.1 (59eed8a2a 2021-11-01)

[Veykril]

Does running cargo check --workspace --message-format=json --manifest-path {path to your projects cargo toml} --all-targets manually in your project work fine?

Though I guess it gets stuck at calling cargo metadata

[luisvgs]

@Veykril hey that worked! The error still appears when opening a project file but it disappears after a few seconds. Do I need to run that command in every project now? How can I prevent this or why is this happening in first place? Thanks in advance for the help.

[Veykril]

Uuh, running that command shouldn't fix the problem for you 😅 I was more interested in seeing whether running cargo check manually would also fail for you or not. This seems rather odd since all that r-a usually does is running cargo metadata and cargo check.

[luisvgs]

@Veykril you are right, I'm still getting the same message in my other projects. I'm running out of ideas.

[lnicola]

When you ran cargo check, did it take a long time?

[tranvnhan]

Not sure if this is the same error:

I think Rust-Analyzer takes some time to load. After that, it seems to be working normally. Though the red status line is quite annoying from time to time.

My setup: neovim + nvim-lsp + rust-analyzer on MacOS.

[khjcph]

Same setup and same issue as @tranvnhan :) Seems to be kindof working though.

[luisvgs]

@khjcph @tranvnhan hey it's the same error I'm facing still! There's a few projects where even rust-analyzer is not able to properly load unless I run cargo check --workspace --message-format=json --manifest-path {path to your projects cargo toml} --all-targets before. It's quite annoying. Did you guys found any workaround or have some insight of what might be causing this misbehavior?

[tranvnhan]

@khjcph @tranvnhan hey it's the same error I'm facing still! There's a few projects where even rust-analyzer is not able to properly load unless I run cargo check --workspace --message-format=json --manifest-path {path to your projects cargo toml} --all-targets before. It's quite annoying. Did you guys found any workaround or have some insight of what might be causing this misbehavior?

I have to learn to live with it 😅. No clue what happens.

[lnicola]

Can anyone share some code where this happens?

[c02y]

I got the same error when I open a Rust project whether I use either Nvim or Emacs

But rust-analyzer is working fine in both of them, function like go-to-definition and auto-completion works fine. It just shows the error in the beginning.

[Veykril]

Is the project open source by any chance? A repro for this is needed to make this actionable.

[champly]

I get the same error when i open project with nvim, this is my configuration. Looks like rust-analyzer problem.