VS Code - crates stop worked across all Cargo.toml files in a large workspace

[ryanolson]

Describe the bug

I've notice that crates as stopped working in my VS Code.

I never realize how amazing this extension was until it stopped working and has be bit stumped as to why it stopped working.

Any thoughts on how to troubleshoot this?

To Reproduce

Latest version of VS Code

Version: 1.85.0
Commit: af28b32d7e553898b2a91af498b1fb666fdebe0c
Date: 2023-12-06T18:17:50.719Z (4 days ago)
Electron: 25.9.7
ElectronBuildId: 25551756
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Darwin arm64 23.1.0

crates == v0.6.5

no custom crates settings in any user/remote/workspace settings.

I have a large workspace in a devcontainer.

I have a rust directory (/work/rust), with a top-level Cargo.toml file and then numerous libraries in /work/rust/lib1, /work/rust/lib2, etc. I also have a /work/python/bindings/Cargo.toml and at least two other rust libraries in /work/submodules/external1, etc.

Expected behavior

Not sure when it stopped working, but I added a new libraries and the usual green check marks stopped working across the entire series of Cargo.toml files.

Screenshots

Desktop (please complete the following information):

Consistent across both Mac and Windows VS Code clients, both of which SSH to a remote machine, then run a devcontainer in the remote machine.

Additional context
Add any other context about the problem here.

[serayuzgur]

@ryanolson what is the current situation?

[ryanolson]

The manual option to trigger a look up works. I need to use it whenever I edit Cargo.toml file.

It might be due to the fact that I have a large workspace consisting of 8+ crates

[serayuzgur]

Can you please provide a mock repository that causes the same bug? So I can debug easily @ryanolson

[kmindi]

I noticed that the Cargo.toml was only recognized by VS Code as "Plain Text". When I installed an extension that adds support for TOML, TOML was detected for the Cargo.toml file and this crates plugin showed again the expected inline version icons.

[ryanolson]

Seems like the issue has been fixed for me.