-
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
cargo (nightly) just hangs there doing little https #4187
Comments
Thanks for the report! Looks like it's buried in libgit2 internals trying to fetch the remote. Could you try using |
Looks similar to #3564 (comment). EDIT: yep, it's exactly the same stack trace and select! The underlying issue was that |
Upstream issue about cancellation: libgit2/libgit2#3334. Anyone wants to re implement |
Just hit the same issue. It's my first time playing around with rust, so I'm a bit stuck at the moment. It just hangs with this: $ RUST_LOG=debug cargo install racer
DEBUG:cargo::sources::config: loading: registry https://github.com/rust-lang/crates.io-index
Updating registry `https://github.com/rust-lang/crates.io-index`
DEBUG:cargo::sources::git::utils: skipping gc as there's only 11 pack files
DEBUG:cargo::sources::git::utils: doing a fetch for https://github.com/rust-lang/crates.io-index
DEBUG:cargo::sources::git::utils: initiating fetch of refs/heads/master:refs/remotes/origin/master from https://github.com/rust-lang/crates.io-index OS: MacOS High Sierra |
Same happens to me when building the guessing game in the tutorial:
Cargo.toml: [package]
name = "gg"
version = "0.1.0"
authors = ["Roberto Dip <dip.jesusr@gmail.com>"]
[dependencies]
rand = "0.3.17" OS: MacOS High Sierra
I have been trying to find a workaround in the issue tracker without success, let me know if I can help in any way :) |
hey @alexcrichton, thanks for the help! I checked out the PR branch locally, but when I tried to compile I faced the same error 😭 . Is there any way to compile cargo without cargo? Just for the sake of clarity, I'm following the instructions in the README:
|
Ah no, unfortunately that's not too easy :( |
Gotcha, if I can help in any way just let me know :) |
Just wanted to inform that since upgrading to |
I'm going to close this as I think a number of intervening updates should mitigate this. |
fix(test): Distinguish 'testname' from escaped arguments When working on clap v4, it appeared that `last` and `trailing_var_arg` are mutually exclusive, so I called that out in the debug asserts in #4187. Unfortunately, I didn't document my research on this as my focus was elsewhere. When updating cargo to use clap v4 in #11159, I found `last` and `trailing_var_arg` were used together. I figured this was what I was trying to catch with above and I went off of my intuitive sense of these commands and assumed `trailing_var_arg` was intended, not knowing about the `testname` positional that is mostly just a forward to `libtest`, there for documentation purposes, except for a small optimization. So it looks like we just need the `last` call and not the `trailing_var_arg` call. This restores us to behavior from 531ce13 which is what I originally wrote the tests against. It looks like #11159 was merged after the last beta branch was made, so we shouldn't need to cherry-pick this into any other release. For reviewing this, I made the test updates in the first commit, showing the wrong behavior. The following commit fixes the behavior and updates the tests to expected behavior. Fixes #11191
I've now been waiting for something like half an hour. The machine has a fast (gbit) internet connection.
The text was updated successfully, but these errors were encountered: