rust-analyzer does not call correct cargo binary

[Taowyoo]

Problem

On VSCode, at latest stable release which just been released within 24 hours v0.3.1868

The extension or maybe rust-analyzer does not call cargo in path. It always calls $HOME/.cargo/bin/cargo

I have custom toolchain in different folder with cargo installed, I add that cargo to path with direnv so when calling cargo in command line it will call that cargo first instead of the default installed one under ``$HOME/.cargo`.

Expect behavior

I assume the rust-analyzer should call the cargo in folders at front of the PATH system variable.

Temporary solution

I solve the issue by rollback the VSCode extension to v0.3.1860

[lnicola]

#16665

[Veykril]

Well that's a nice conflict of interests we have here now

[Taowyoo]

Thank you for quick response.