-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Bump API schema to 6ba1c004 #14979
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
Merged
Merged
Bump API schema to 6ba1c004 #14979
Changes from all commits
Commits
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
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.
Potential bug: The
fetchcall inresolveOpenAPIlacks HTTP status checking before parsing the JSON response, which can crash the build process on failure.Description: The
resolveOpenAPIfunction fetches a schema from a GitHub URL. It does not check the HTTP response status before attempting to parse the body withresponse.json(). If theSENTRY_API_SCHEMA_SHAis invalid, GitHub returns a 404 response with an HTML body. Attempting to parse this HTML as JSON throws aSyntaxError. Because this function is executed during static site generation, this unhandled exception will crash the entire build process, preventing deployment. This failure pattern has occurred previously, as seen in a past Sentry issue.Suggested fix: After the
fetchcall, check theresponse.okstatus. If the response is not successful, throw a descriptive error to fail the build gracefully instead of letting theresponse.json()call raise an unhandledSyntaxError.severity: 0.85, confidence: 0.95
Did we get this right? 👍 / 👎 to inform future reviews.