Fix GitHub search rate throttling#24
Merged
Merged
Conversation
125b813 to
d244d62
Compare
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\n- scale REST throttling buffer to the actual GitHub bucket limit instead of assuming the 5k core REST bucket\n- avoid immediate sleep loops for GitHub search buckets, which are often around 30/min\n- serialize per-user commit/PR search calls so they do not race the shared throttle state\n\n## Why\nThe live refresh was sleeping immediately with repeated:\n\n
\n[throttle] Approaching rest rate limit — sleeping 60s until reset.\n\n\nThat happened because GitHub search exposes a much smaller REST-style bucket, and the old hard-coded 100-request REST buffer is larger than the whole search bucket.\n\n## Verification\n- pnpm run check\n- pnpm run test