-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Output of cargo metadata may not be machine-readable if the registry needs to be updated #2661
Comments
Oh and I'm running |
Actually we want that output in IntelliJ-Rust :) We can make However I would argue that quite by default is a bad behavior. #1473 seems like the correct solution here. Another option is to better document current behavior and to make sure that something ( |
Interesting! Sounds like #1473 is the right solution |
closed by #2722 |
🎊 |
So this will hit stable Rust with 1.10? I need to remember to fix progress reporting on the IntelliJ side |
Yeah that sounds right! |
Repro steps:
rm Cargo.lock
cargo metadata
Observe that the JSON output is preceded by:
A workaround is possible by running
cargo metadata --quiet
, but I can't really imagine that output being wanted in a command whose output is supposed to be machine-readable.It's a pretty easy edge case to miss since usually your registry doesn't need to be updated. It bit me in SSheldon/rust-test-ios#3.
The text was updated successfully, but these errors were encountered: