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 hangs at "Resolving dependency graph..." #11454

Open
sorpaas opened this issue Dec 5, 2022 · 2 comments
Open

Cargo hangs at "Resolving dependency graph..." #11454

sorpaas opened this issue Dec 5, 2022 · 2 comments
Labels
A-dependency-resolution Area: dependency resolution and the resolver C-bug Category: bug E-hard Experience: Hard Performance Gotta go fast! S-needs-team-input Status: Needs input from team on whether/how to proceed.

Comments

@sorpaas
Copy link

sorpaas commented Dec 5, 2022

Problem

Building the following project, the build process hangs at Resolving dependency graph...

Steps

  1. Clone https://github.com/corepaper/morum/tree/f70f328621513dae95a4c8833878332be9211a4e
  2. Run build, and it should work.
  3. Uncomment line matrix-sdk = { version = "0.6", default-features = false, features = ["e2e-encryption", "sled", "rustls-tls"] } in Cargo.toml to add the dependency.
  4. Cargo hangs at Resolving dependency graph...

Possible Solution(s)

No response

Notes

No response

Version

Tried both stable and nightly releases:

cargo 1.65.0 (4bc8f24d3 2022-10-20)
cargo 1.67.0-nightly (f6e737b1e 2022-12-02)
@sorpaas sorpaas added the C-bug Category: bug label Dec 5, 2022
sorpaas added a commit to corepaper/morum that referenced this issue Dec 6, 2022
rel rust-lang/cargo#11454

Seems like removing the `full` feature of `ruma` magically makes dep
resolution work again.
@ehuss
Copy link
Contributor

ehuss commented Dec 10, 2022

I suppose this is #4066 more or less. The resolver is running into conflicts, backing up and trying a different version, and then repeatedly failing. It could take hours or more for it to try all permutations.

@Eh2406 Is there anything to learn from this issue? Should it be closed in favor of #4066 (or #5284)?

@Eh2406
Copy link
Contributor

Eh2406 commented Dec 10, 2022

Yes, my best guess is that the resolver is trying an extraordinary number of permutations without generalizing to see what the real problem is. Real-world examples are always interesting. When will I have time to follow up on this example, to see what properties make it slow? I don't know that I will make time for it, sorry.

@ehuss ehuss added the A-dependency-resolution Area: dependency resolution and the resolver label Dec 11, 2022
@weihanglo weihanglo added S-needs-team-input Status: Needs input from team on whether/how to proceed. E-hard Experience: Hard Performance Gotta go fast! labels May 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-dependency-resolution Area: dependency resolution and the resolver C-bug Category: bug E-hard Experience: Hard Performance Gotta go fast! S-needs-team-input Status: Needs input from team on whether/how to proceed.
Projects
None yet
Development

No branches or pull requests

4 participants