-
Notifications
You must be signed in to change notification settings - Fork 212
Some releases where missed to build #1912
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
Comments
Looks like it wasn't seen for some reason, production logs from the registry checks before/after the publish event:
Relevant commits in https://github.com/rust-lang/crates.io-index: > git log --format='%ai %h %s' --since='2022-11-17 00:00' an/si/ansi-color-codec
2022-11-17 17:26:27 +0000 92c18bdf30a Yanking crate `ansi-color-codec#0.3.5`
2022-11-17 17:26:25 +0000 1533f8e863a Yanking crate `ansi-color-codec#0.3.4`
2022-11-17 17:26:00 +0000 da97cd0243b Updating crate `ansi-color-codec#0.3.11` It's likely a bug in |
@Nemo157 thank you for digging into this! when fixed, is it worth running our consistency-check command? Does it still work? |
Not sure, this should be very rare, I think it only happens when a crate is published and yanked multiple times within a minute to get picked up in the same index check. That said, it did already happen within two weeks of the crates-index-diff update 🙃 |
The latest version of |
#1935 was merged & deployed, which should fix this reliably. Since we need to find other releases we missed for this to be really solved, I'll leave this issue open until we ran (and fixed?) the consistency check. |
Crate name
ansi-color-codec
Build failure link
N/A
Additional details
I updated ansi-color-codec to 0.3.11 today, but it was never built on docs.rs.
It is neither in the queue nor is there a failed build logged for this version.
The docs build fine on my dev machine with
rustdoc 1.63.0 (4b91a6ea7 2022-08-08)
.Any idea what's going on?
The text was updated successfully, but these errors were encountered: