Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error during execution of cargo metadata: error: --all-features is not allowed #2040

Closed
Matthias247 opened this issue Oct 21, 2019 · 6 comments

Comments

@Matthias247
Copy link
Contributor

I just updated rust-analyzer to the latest git revision 6b9bd7b. Here I get the following error message when opening VsCode:

rust-analyzer failed to load workspace: cargo metadata failed: Error during execution of cargo metadata: error: --all-features is not allowed in the root of a virtual workspace

This didn't happen with the last revision I build (unfortunately I don't have the commit ID, but it should have been roughly 2 weeks old).

Unfortunately I don't have the code online yet, but it's nothing very special. Just a cargo workspace with 3 subprojects in it. One of them specifies features on some dependencies, the others don't deal with features at all.

@Matthias247
Copy link
Contributor Author

Oh, I also updated rustc to the latest nightly version. Maybe that made a difference by bringing in a different cargo revision?

@Matthias247
Copy link
Contributor Author

Seems like intellij-rust has the same issue: intellij-rust/intellij-rust#4541

@Matthias247
Copy link
Contributor Author

I confirmed this is caused by the rustc update. Going back via

rustup install nightly-2019-10-15
rustup default nightly-2019-10-15
rustup component add rust-src

fixes the issue.

Feel free to close if you think this is a temporary rustc bug. Or leave open if there had been a rustc output format change that rust-analyzer needs to adopt to.

@sinkuu
Copy link
Contributor

sinkuu commented Oct 21, 2019

This is a temporary cargo bug. rust-lang/cargo#7525

@Matthias247
Copy link
Contributor Author

Good to know! So seems like there is nothing to do for the team.

You might want to consider still leaving this open for a couple of days until nightly is fixed, so that others stumbling over the same issue see it and don't create duplicates.

@Matthias247
Copy link
Contributor Author

This is no longer an issue with newer nightlies

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants