Skip to content

cargo update hangs in cargo::core::resolver::activate_deps_loop #4108

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

Closed
codewiz opened this issue May 28, 2017 · 4 comments
Closed

cargo update hangs in cargo::core::resolver::activate_deps_loop #4108

codewiz opened this issue May 28, 2017 · 4 comments

Comments

@codewiz
Copy link

codewiz commented May 28, 2017

I hit this while running "cargo update" on the master branch of https://github.com/paritytech/parity .

Trace: cargo-update.txt
Produced with RUST_LOG=cargo::core::resolver=trace cargo generate-lockfile

Cargo.lock.txt
Cargo.toml.txt

@codewiz
Copy link
Author

codewiz commented May 28, 2017

Affects both cargo 1.18 and cargo nightly 0.20.0-nightly (9fcdbb4 2017-05-22)

@bennofs
Copy link
Contributor

bennofs commented May 28, 2017

Looks like the problem is that multihash depends on ring ~0.7.1 which has been yanked --> the solver never finds a solution for ring and backtracks through the entire search space.

@bennofs
Copy link
Contributor

bennofs commented May 28, 2017

The activation/backtracking chain seems to go something like this:

... -> isatty -> bitflags -> rpassword -> semver -> pretty_assertions -> difference -> matches -> quine-mc_cluskey -> miow -> multihash -> ring (fail)

and for each of the packages in the chain, cargo tries a few possibilities (and the chain is probably longer)

@alexcrichton
Copy link
Member

Thanks for the investigation @bennofs! In that case I'm going to close this in favor of #4066 as I think it's a dupe of that issue.

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

3 participants