Repository navigation
fix: avoid hour-long merge backoff from request ID digits - #311
Merged
Merged
Conversation
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.
An Azure HTTP 503 containing
401in its request ID was classified as an authentication failure, imposing a one-hour retry delay on the first failed merge. Recognize 401/403 only in explicit HTTP/status syntax; recognize transient HTTP responses before incidental timeout configuration text. Actual authentication, data/configuration, and unresolved ownership failures retain their existing retry restrictions.Regression coverage includes the production Azure error (URL anonymized), both observed request IDs, 403 in request IDs, real 401/403 formats, 429/503, and derived retry deadlines. All 16 merge library tests passed, including the eight real-etcd integration tests. This changes future failure classification; it does not reset persisted retry records or ownership.