Always loading on checking

[aurexav]

Restart doesn't help.

I've to killall && cargo build. Otherwise I can't do any cargo operation.

[aurexav]

I also disable the checkonsave in my settings.

[aurexav]

BTW, I often get this error in recently updates:

[Error - 9:09:12 PM] Registering progress handler for token rustAnalyzer/indexing failed.
Error: Progress handler for token rustAnalyzer/indexing already registered
	at Object.onProgress (/root/.vscode-server/extensions/matklad.rust-analyzer-0.3.549-nightly/out/src/main.js:5384:23)
	at LanguageClient.onProgress (/root/.vscode-server/extensions/matklad.rust-analyzer-0.3.549-nightly/out/src/main.js:13071:45)
	at new ProgressPart (/root/.vscode-server/extensions/matklad.rust-analyzer-0.3.549-nightly/out/src/main.js:11050:41)
	at createHandler (/root/.vscode-server/extensions/matklad.rust-analyzer-0.3.549-nightly/out/src/main.js:14415:34)
	at handleRequest (/root/.vscode-server/extensions/matklad.rust-analyzer-0.3.549-nightly/out/src/main.js:4917:41)
	at processMessageQueue (/root/.vscode-server/extensions/matklad.rust-analyzer-0.3.549-nightly/out/src/main.js:4781:17)
	at Immediate._onImmediate (/root/.vscode-server/extensions/matklad.rust-analyzer-0.3.549-nightly/out/src/main.js:4771:13)
	at processImmediate (internal/timers.js:456:21)

[lnicola]

Is that on https://github.com/libp2p/rust-libp2p?

[aurexav]

I'm on substrate.

Which was listed here https://github.com/libp2p/rust-libp2p#notable-users.

This is a sub-sub dep of my project.

And I think this might not relate to a specific dep.

After few times restart, now it stuck(always loading) at another dep.

[lnicola]

I can't reproduce on substrate, but it does take ages to check.

[aurexav]

I can't reproduce on substrate, but it does take ages to check.

Does this whole process need a good network env?

[lnicola]

It should be enough if cargo check works for you in a terminal.

[aurexav]

It should be enough if cargo check works for you in a terminal.

Cargo check works good. But curios why this always show loading.

Also there's a similar issue.

When I run cargo fmt in terminal directly, it response very quick.

But if I use rust-analyzer to call cargo fmt(such as format shortcut). It will show a loading bar at the top of the vscode and take a long time to finish the format.

[lnicola]

But if I use rust-analyzer to call cargo fmt(such as format shortcut). It will show a loading bar at the top of the vscode and take a long time to finish the format.

I noticed this too. I'm not sure, but I think we might be busy processing some other requests, so we take a while to start rustfmt. Or it might be something completely different.

[lnicola]

@AurevoirXavier would you mind trying a nightly version? The project loading hang might have been fixed in #8600 and the (harmless) progress handler error in #8606.

[aurexav]

How?

It will be updated automatically?

[lnicola]

It will be updated on Monday or you can set "rust-analyzer.updates.channel": "nightly" in settings.json.

[aurexav]

[Error - 9:25:10 PM] Registering progress handler for token rustAnalyzer/Indexing failed.
Error: Progress handler for token rustAnalyzer/Indexing already registered
	at Object.onProgress (/root/.vscode-server/extensions/matklad.rust-analyzer-0.3.566-nightly/out/src/main.js:5384:23)
	at LanguageClient.onProgress (/root/.vscode-server/extensions/matklad.rust-analyzer-0.3.566-nightly/out/src/main.js:13071:45)
	at new ProgressPart (/root/.vscode-server/extensions/matklad.rust-analyzer-0.3.566-nightly/out/src/main.js:11050:41)
	at createHandler (/root/.vscode-server/extensions/matklad.rust-analyzer-0.3.566-nightly/out/src/main.js:14415:34)
	at handleRequest (/root/.vscode-server/extensions/matklad.rust-analyzer-0.3.566-nightly/out/src/main.js:4917:41)
	at processMessageQueue (/root/.vscode-server/extensions/matklad.rust-analyzer-0.3.566-nightly/out/src/main.js:4781:17)
	at Immediate._onImmediate (/root/.vscode-server/extensions/matklad.rust-analyzer-0.3.566-nightly/out/src/main.js:4771:13)
	at processImmediate (internal/timers.js:456:21)

Loading passed.

But indexing stuck.