-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Update Cargo #48986
Update Cargo #48986
Conversation
@bors: r+ |
📌 Commit 759fa2c has been approved by |
@bors r- Several tests for cargo are failing due difference between clap and docopt.
|
Not exactly, it's because the tests are using error messages from clap version X, and on rust-lang/rust, clap is on version Y. Guess I'll need to loosen tests up a bit! |
On the other hand, the easier route is just to update clap here :) I am not 100% sure that relaxing the tests would be a better solution: it's important to check that the error messages actually look reasonable to protect from, say, potential clap regressions. Perhaps updating the error messages once in a while won't be such a big chore in practice? Note that we'll hit the need of update in Cargo first, because its CI does not use lockfile, and always uses the latest clap. |
@bors: r+ |
📌 Commit 5be1d82 has been approved by |
☔ The latest upstream changes (presumably #49014) made this pull request unmergeable. Please resolve the merge conflicts. |
Resolved conflicts and updated Cargo even more, to include rust-lang/cargo#5188 as well |
Found a regression with clap, so don't r+ this just yet :) |
Updated with the fix for the regression. |
@bors: r+ |
📌 Commit a4ed1ad has been approved by |
☔ The latest upstream changes (presumably #48097) made this pull request unmergeable. Please resolve the merge conflicts. |
This notably includes * rust-lang/cargo#5152 * rust-lang/cargo#5188 The first one switches cargo from docopt to clap ( we also update to the latest calp in this repository), the second one should help us to unify feature flags for Cargo itself and RLS, and build Cargo libray only once.
rebased |
@bors: r+ |
📌 Commit b15b023 has been approved by |
Update Cargo r? @alexcrichton Let's put new clap argument parsing in production to see if anything dies in flames :)
☀️ Test successful - status-appveyor, status-travis |
Tested on commit rust-lang/rust@8aa27ee. Direct link to PR: <rust-lang/rust#48986> 💔 rls on windows: test-pass → build-fail (cc @nrc). 💔 rls on linux: test-pass → build-fail (cc @nrc).
|
The RLS itself is already updated (rust-lang/rls@c0f07b3), so only submodule update in rust-lang/rust is required. |
I am not sure if it's related to this, but it seems that third party Cargo commands no longer work by executing $ cargo install-update -a
error: The subcommand 'install-update' wasn't recognized
Did you mean 'install'?
If you believe you received this message in error, try re-running with 'cargo -- install-update'
USAGE:
cargo [OPTIONS] [SUBCOMMAND]
For more information try --help
$ cargo -- install-update -a
error: The subcommand 'install-update' wasn't recognized
Did you mean 'install'?
If you believe you received this message in error, try re-running with 'cargo -- install-update'
USAGE:
cargo [OPTIONS] [SUBCOMMAND]
For more information try --help Stable works fine: $ cargo +stable install-update -a
Updating registry `https://github.com/rust-lang/crates.io-index`
Package Installed Latest Needs update
bindgen v0.33.2 v0.33.2 No
No packages need updating. |
Thank you so much for the report @messense ! Opened an issue at the Cargo tracker: rust-lang/cargo#5201, and investigating. Looks like not every external subcommand is broken, only those that are named closely to the built-in ones. |
Update clap This should fix a regression in Cargo after swithing to clap, when an external subcommand was not discovered, if its name was close to a built in command. bug report: #48986 (comment) fix: clap-rs/clap#1215
Update clap This should fix a regression in Cargo after swithing to clap, when an external subcommand was not discovered, if its name was close to a built in command. bug report: #48986 (comment) fix: clap-rs/clap#1215
Update clap This should fix a regression in Cargo after swithing to clap, when an external subcommand was not discovered, if its name was close to a built in command. bug report: rust-lang#48986 (comment) fix: clap-rs/clap#1215
r? @alexcrichton
Let's put new clap argument parsing in production to see if anything dies in flames :)