[code] rust-analyzer failed to discover workspace

[0x8f701]

I just discovered that rust extensions seems activated accidently in my cpp project, it shows this:

[lnicola]

Can you upload it somewhere? Or trim it down to see what's triggering it?

Is it a mixed Rust/C++ project? Do you have a Cargo.toml in there?

[0x8f701]

Can you upload it somewhere? Or trim it down to see what's triggering it?

Is it a mixed Rust/C++ project? Do you have a Cargo.toml in there?

I'll try to do it, it's a pure c++/nodejs/vuejs project, there aren't any rust related things

[heaths]

I'm seeing this in a large monorepo full of file extensions, namely https://github.com/azure/azure-sdk-for-net. Perhaps this error doesn't need to display an error dialog but just trace to its associated output?

[heaths]

Not sure it helps, but this was the only message I saw printed to the "Rust Analyzer Language Server" output window:

[ERROR rust_analyzer] failed to find any projects in [AbsPathBuf("c:\\src\\azure-sdk-for-net")]

[JonnyBGod]

I am also getting this error message on mostly every non rust project. And also see rust-analyser running for these projects where it should be ignore.

[lnicola]

I'm seeing this in a large monorepo full of file extensions, namely https://github.com/azure/azure-sdk-for-net. Perhaps this error doesn't need to display an error dialog but just trace to its associated output?

Are you opening any file? I can't reproduce at 1f88c0d7e2577cb740f1a0110f3318a9aac6f0ca:

Can you try with a fresh clone of the repo, preferably on a local drive?

[0x8f701]

@lnicola no I just ran code .

[ishowta]

Probably the same issue as #2533 (comment).

If so, it's because VSCode forces run the extension at scan directory timeout (microsoft/vscode#73656).

[lnicola]

This was actually mentioned in the Code release notes: microsoft/vscode#110510 (comment). Unfortunately, that fix does nothing for us because we set workspaceContains:**/Cargo.toml.

[heaths]

There's another issue open on the performance of this depth search, and I proposed a max-depth setting that could help this. We did this for VSIX extension discovery in VS and a max depth of, IIRC, 3 made a huge difference. For this extension, perhaps taking a look at some popular repos and determining depth would be handy. For one project I'm working on, 4 would be sufficient.

[heaths]

I should've read the whole URL in the address bar. Wrong repo, but a workaround was suggested that accomplishes what I mentioned above:

workspaceContains:*/example.txt
workspaceContains:*/*/example.txt
workspaceContains:*/*/*/example.txt

[lnicola]

No, that's a good idea, thanks for posting.