Handle github secondary rate limit errors #103589
Draft
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
Co-authored-by: jenn.muengtaweepongsa <jenn.muengtaweepongsa@sentry.io>
github-actions
bot
added
the
Scope: Backend
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.
This PR fixes an issue where GitHub's secondary rate limits, which return a 403 Forbidden status, were not properly handled during commit context blame fetching. Previously, these unhandled 403s would propagate and create false-positive Sentry issues.
The change introduces logic to detect 403 responses from GitHub that specifically indicate a "secondary rate limit". When detected, these errors are now re-raised as
ApiRateLimitedError. This allows the existingCommitContextIntegrationto properly catch and handle them as rate-limit events, halting the integration lifecycle gracefully and preventing the creation of unnecessary Sentry issues.A new test case has been added to ensure this specific scenario is correctly handled.
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.