Can't stop cargo check

[thewh1teagle]

I use rust-analyzer rarely because it works very slow for me.
When rust-analyzer server is stopped, every time I save something it runs cargo check in vscode
Even when the settings of check_on_save is false here
Also, even when it's running, I can't stop cargo check in genreral.

rust-analyzer version: 0.3.1807

rustc version: rustc 1.75.0 (82e1608df 2023-12-21)

relevant settings: settings.json available in vibe

[Veykril]

There is no way for r-a to invoke cargo check when the server is stopped as the server is the process that invokes it.

[thewh1teagle]

@Veykril
You absolutely right. it was Cargo extension!

To disable I needed to add in settings.json:

{
  "cargo.automaticCheck": false
}

[lnicola]

Are you using the Rust Extension Pack? I wonder how many people are running cargo check twice without knowing. It's not a problem on small to medium projects, but still.

[Veykril]

We should probably check if the extension is installed and checkOnSave is set. Similar to how we warned about the old rust extension.

[thewh1teagle]

@lnicola
It's a real problem even on small projects.
It was very annoying to use r-a + cargo. It slowed down my entire PC because it's similar to cargo build
So almost every save, change etc... I had slowness.
Now I turned off r-a and disabled cargo check on save in both r-a and cargo extensions and finally I can move faster.
Now I turn on r-a only when working with new crates to learn them faster.

@Veykril
I think it worth checking if cargo extension already run it. not sure why we need cargo check and if it really ran twice, but I guess that anyway worth not even trying to run if already.

[thewh1teagle]

Does it possible to disable r-a to run when I open the project? and start only manually when I need?

[Young-Flash]

Does it possible to disable r-a to run when I open the project? and start only manually when I need?

do you mean

[Young-Flash]

We should probably check if the extension is installed and checkOnSave is set. Similar to how we warned about the old rust extension.

I'd like to try working on it

[thewh1teagle]

Does it possible to disable r-a to run when I open the project? and start only manually when I need?

do you mean

No.
r-a should store the state on the disk if the server should start or not.
And then if I stopped the server and reopened vscode it shouldn't start automatically.

[lnicola]

As you must already know, you can disable and enable it per VS Code workspace, which is similar to that.

If it feels too slow, you can also try to disable cache priming in the settings. It won't make it any faster, but projects will appear to take less time to load.

It might also be interesting to see why it's so slow. I've never used Tauri, is there any difference between how it behaves on the UI code and the rest?

[thewh1teagle]

As you must already know, you can disable and enable it per VS Code workspace, which is similar to that.

If it feels too slow, you can also try to disable cache priming in the settings. It won't make it any faster, but projects will appear to take less time to load.

It might also be interesting to see why it's so slow. I've never used Tauri, is there any difference between how it behaves on the UI code and the rest?

I see, thanks for the point about workspace setting in vscode.
I think that a setting like rust-analyzer.autoStart is simple useful and effective

[thewh1teagle]

As you must already know, you can disable and enable it per VS Code workspace, which is similar to that.

If it feels too slow, you can also try to disable cache priming in the settings. It won't make it any faster, but projects will appear to take less time to load.

It might also be interesting to see why it's so slow. I've never used Tauri, is there any difference between how it behaves on the UI code and the rest?

I think that r-a became slow to me since I started split my projects into multiple workspaces, and also tauri has many dependencies, and another special thing with tauri is "hot reload" everytime you save it recompile so There's a race between cargo check and checks from r-a and the regular build, and the first blocks for the second

You can easily try the project by

1. git clone
2. cargo install tauri-cli
3. Have nodejs
4. in desktop/src-tauri cargo tauri dev

[lnicola]

Yeah, cargo check and cargo build should block each other. If you run cargo check twice, one will run and the other one will wait until it's ready, the complete more or less instantly.

Anyway, I disable cargo check and enable the experimental diagnostics, which takes care of that. But I guess even that is too slow for you?

[thewh1teagle]

@lnicola
I didn't experimented with different settings, I'll try.
All I can say is since I disabled r-a server (manually) and cargo extension my builds finally much faster and very lighter!