Repository navigation
fix(server): pull request links whose reads keep failing back off instead of re-reading every minute #31969
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
Open
juliusmarminge
wants to merge
8
commits into
main
Choose a base branch
from
fix/issue-31954
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+106
−1
Open
fix(server): pull request links whose reads keep failing back off instead of re-reading every minute #31969
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
f188c79
test(server): reproduce #31954, failing pull request reads are retrie…
juliusmarminge 8edf3a2
fix(server): pull request links whose reads keep failing back off ins…
juliusmarminge 4397f86
test(server): pin the failed pull request read backoff cap and its re…
juliusmarminge 9eab4ba
test(server): drop the never-synced backoff test the exact schedule t…
juliusmarminge 0974f3a
Merge remote-tracking branch 'origin/main' into fix/issue-31954
juliusmarminge cc131a6
test(server): assert a failed refresh doubles the pull request read b…
juliusmarminge 303e5d3
Merge remote-tracking branch 'origin/main' into fix/issue-31954
juliusmarminge 42add88
test(server): drop the newly linked backoff test the schedule test al…
juliusmarminge File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After a non-rate-limit failure this always records
failedReads(1m, then doubling to the 15m slow interval). The PR body says interruptions are excluded from backoff, but the branch visible here only special-casesrateLimitRetryAt.Does an Effect interruption (for example stopping the reactor mid-sweep, or a fiber interrupt while
glabis still running) get filtered before thiselse, or can it leave the link backed off until a later successful read clears the map? If interruptions already bail out earlier this is fine — asking because a restart would otherwise make a flaky host look "paused" for up to 15 minutes with no host pause recorded.