github repo updater: support new secondary rate limits#3184
Merged
syphar merged 1 commit intorust-lang:mainfrom Feb 7, 2026
Merged
github repo updater: support new secondary rate limits#3184syphar merged 1 commit intorust-lang:mainfrom
syphar merged 1 commit intorust-lang:mainfrom
Conversation
github-actions
bot
added
the
S-waiting-on-review
GuillaumeGomez
approved these changes
Feb 7, 2026
github-actions
bot
added
S-waiting-on-deploy
syphar
removed
the
S-waiting-on-deploy
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
2 participants
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.
will "hide" the rate limit error here:
https://rust-lang.sentry.io/issues/7210241181/?environment=production&project=5499376&query=is%3Aunresolved&referrer=issue-stream
by adding it to our normal rate-limit handling, which means we just stop & try again the next hour.
Let's see if that's enough.
We'll have to watch if we still can fetch enough repo updates or if the data is too outdated at some point.
( I still have the impression that github raises the error quicker than it does if I do the same queries locally )