ci(release): harden embedded curl vs HF 429; badge → v0.3.3 - #52
Merged
Conversation
The embedded jobs fetch the ~1.1 GB BitNet GGUF 3x per release; on v0.3.3 HuggingFace returned HTTP 429 and --retry-delay 2 was too short, failing the x86 embedded job (fixed by re-running). Bump all three embedded curls to --retry 5 --retry-delay 15 --retry-all-errors so a transient 429 is ridden out. README status badge bumped v0.3.2 -> v0.3.3 (now the latest release).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two small follow-ups after the v0.3.3 release.
--retry-delay 2was too short, so the x86 embedded job failed (recovered by re-running the job). All three embeddedcurls now use--retry 5 --retry-delay 15 --retry-all-errorsto ride out a transient rate-limit.v0.3.2→v0.3.3(now the latest release).No code changes; YAML validated.