feat: retry op read with exponential backoff for flaky wifi#52
Merged
Conversation
Single timeout fails on slow connections; retrying with 2s/4s/8s backoff gives 3 chances across ~14s without penalizing fast networks. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Addresses review feedback: variable leaked into function scope, and "retrying…" was misleading on the final attempt. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
The change adds a retry loop with increasing timeouts (2s → 4s → 8s) for op read in _load_gh_token(). No BLOCK criteria met:
VERDICT: PASS |
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.
Summary
op readwith retry loop using 2s/4s/8s exponential backoffcould not retrieve GH_TOKENwarnings on slow networksTest plan
CLAUDE_DEBUG=true claudeon slow wifi — debug log should show retry attempts🤖 Generated with Claude Code