You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in vscode the rust-analyzer log is a bit more helpfull with:
rust-analyzer failed to load workspace: Failed to load the project at /home/bennet/git/project/Cargo.toml: Failed to query rust toolchain version at /home/bennet/git/project, is your toolchain setup correctly?: cd "/home/bennet/git/project" && "/home/bennet/.cargo/bin/cargo" "--version" failed, exit status: 1
stderr:
error: error parsing manifest: TOML parse error at line 1478, column 23
|
1478 | [[pkg.rust.target.aarc<!--a bunch of nul bytes-->win.extensions]]
| ^
invalid table header
expected `.`, `]]`
It shows a bunch of null bytes where `<!--a bunch of nul bytes-->` is.

This is under WSL2 Ubuntu on Windows 11, I believe the corruption might be due to a recent export import of the WSL Image/distribution.
But I think cargo should handle this better, at least a filename of the manifest that failed to parse would be good.
Steps
somehow corrupt the manifest file
run any of the command show above
Possible Solution(s)
Include manifest path in error message
Notes
No response
Rustup version
$> rustup --versionrustup 1.27.1 (54dd3d00f 2024-04-24)info: This is the version for the rustup toolchain manager, not the rustc compiler.info: The currently active `rustc` version is `rustc 1.78.0 (9b00956e5 2024-04-29)`
Verification
Problem
Independent of the directory and command I run cargo errors with the following error message:
in vscode the rust-analyzer log is a bit more helpfull with:
It shows a bunch of null bytes where `<!--a bunch of nul bytes-->` is.
This is under WSL2 Ubuntu on Windows 11, I believe the corruption might be due to a recent export import of the WSL Image/distribution.
But I think cargo should handle this better, at least a filename of the manifest that failed to parse would be good.
Steps
Possible Solution(s)
Include manifest path in error message
Notes
No response
Rustup version
Installed toolchains
OS version
The text was updated successfully, but these errors were encountered: