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

cargo plugin sub commands no longer work in nightly version #5212

Closed
sagiegurari opened this issue Mar 20, 2018 · 5 comments
Closed

cargo plugin sub commands no longer work in nightly version #5212

sagiegurari opened this issue Mar 20, 2018 · 5 comments

Comments

@sagiegurari
Copy link

All subcommands that come from external crates stopped working with the latest nightly cargo.

rustc --version
rustc 1.26.0-nightly (a04b88d19 2018-03-19)
rustup --version
rustup 1.11.0 (e751ff9f8 2018-02-13)
cargo --version
cargo 1.26.0-nightly (d6c3983 2018-03-16)

Installing /home/travis/.cargo/bin/cargo-make
The command "cargo install --debug cargo-make" exited with 0.
0.04s$ cargo make ci-flow
error: Found argument 'ci-flow' which wasn't expected, or isn't valid in this context
USAGE:
    cargo [SUBCOMMAND]
For more information try --help

See build example: https://travis-ci.org/sagiegurari/cargo-make/jobs/355826819#L530

@matklad
Copy link
Member

matklad commented Mar 20, 2018

Yep, that's a known issue that I've broken all subcommands on nightly :-(

The issue is already fixed in Cargo, the PR with Cargo update to rust-lang/rust is rust-lang/rust#49182

@anp
Copy link
Member

anp commented Mar 23, 2018

Looks like rust-lang/rust#49182 merged a couple of days ago, although I'm not sure which nightly it'll ride -- with nightly-2018-03-21 from rustup I'm seeing cargo 1.26.0-nightly (d6c3983fe 2018-03-16).

@sagiegurari
Copy link
Author

@matklad when can we expect a fix for this? I tried the latest nightly and its still failing.

@ehuss
Copy link
Contributor

ehuss commented Mar 24, 2018

@sagiegurari It looks like a new nightly has been pushed with the update to cargo.

@sagiegurari
Copy link
Author

Thanks @ehuss you are right. Works great now.

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

4 participants