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

Freeze with the sparse protocol #692

Closed
loyd opened this issue Aug 4, 2023 · 2 comments
Closed

Freeze with the sparse protocol #692

loyd opened this issue Aug 4, 2023 · 2 comments

Comments

@loyd
Copy link

loyd commented Aug 4, 2023

I'm trying to release all crates in a workspace with the latest stable toolchain (1.71.1) and cargo-release (0.24.11) and after the Published step the whole process just freezes and nothing happens

note: Waiting for `elfo-dumper v0.2.0-alpha.5` to be available at registry `crates-io`.
You may press ctrl-c to skip waiting; the crate should be available shortly.
   Published elfo-dumper v0.2.0-alpha.5 at registry `crates-io`

After enabling the old protocol, it works as expected:

[registries.crates-io]
protocol = "git"
@loyd loyd changed the title Freeze with the parse protocol Freeze with the sparse protocol Aug 4, 2023
@imp
Copy link
Contributor

imp commented Aug 8, 2023

It seems that it is not a freeze, but rather long delay caused by cargo-release updating crates.io git index (which is falling behind after switch to sparse index by default in 1.71). Naturally if git index is sufficiently up-to-date the refresh doesn't take long.

Perhaps crates-index dependency may be updated to latest version (0.19 -> 2.1) to allow cargo-release to utilize sparse index instead?

@epage
Copy link
Collaborator

epage commented Nov 1, 2023

Closing in favor of #679 (different symptom, same root cause)

@epage epage closed this as not planned Won't fix, can't repro, duplicate, stale Nov 1, 2023
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

Successfully merging a pull request may close this issue.

3 participants