fix(platform): handle unexpected github-graphql error #22512
Merged
Conversation
This file contains 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
rarkins
requested changes
May 31, 2023
Co-authored-by: Rhys Arkins <rhys@arkins.net>
…ingh/renovate into fix/improve-err-msg
rarkins
approved these changes
May 31, 2023
|
🎉 This PR is included in version 35.105.4 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
6 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Changes
There are some graphQL errors that are returned with a 200 status code, eg. RATE_LIMITED. There isn't any official documentation for these errors so we can't be sure if it happens only for
rate-limitedor not. Therefore, I have added a new error-constantPLATFORM_UNKNOWN_ERRORfor such errors.Context
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: