Clippy as command leads to no diagnostics

[augustocdias]

If I set the setting rust-analyzer.checkOnSave.command to clippy I'm getting no diagnostics (on multi project workspaces) since last week's rust-analyzer update. Is this an issue with coc or rust-analyzer?

I could reproduce the issue on VSCode and NeoVim+Coc (https://github.com/fannheyward/coc-rust-analyzer/issues/833)

[equal-l2]

Any updates here?

[semicoleon]

I just ran into something similar, but it was because I switched to the nightly toolchain with rustup and hadn't added clippy to it yet. After rustup component add clippy (with the relevant toolchain selected) things started working again.

RA didn't display any warning about the command not being found that I could see.

Does running cargo clippy in the project folder work?

[augustocdias]

I don't use nightly and yes it works

[Leandros]

Same issue here, I get no diagnostics on a workspace project. Running cargo clippy manually works.

[kkharji]

Same issue

[Veykril]

This needs a reproducer for us to be actionable, or at least some logs.

[Leandros]

I can reproduce it easily. How can I get you some logs?

[Veykril]

On VSCode you can get the logs here

[Veykril]

Are people still running into this? We'd need to see a repro this reproduces on

[pattop]

Still happens for me.

Sorry, false positive. The build was failing somewhere else due to noDefaultFeatures being set.