Repository navigation
Core page: the 429 hop is a pause, not a failure - #83
Merged
Merged
Conversation
Since core 0.79.0 an upstream that answers 429 is paused and the request moves on or waits; it no longer counts as a failure. The failover tile and the terminal log show it as paused, faded instead of struck through. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Since core 0.79.0 an upstream that answers 429 is paused and the request moves on or waits; it no longer counts as a failure. The Core page's failover tile and terminal log now show that hop as
429 · paused 30s, faded instead of struck through.pnpm buildpasses.🤖 Generated with Claude Code