-
Notifications
You must be signed in to change notification settings - Fork 13k
fix(core): decode byte-array encoded API error messages #19855
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
Open
Rohan-Mohite14
wants to merge
6
commits into
google-gemini:main
Choose a base branch
from
Rohan-Mohite14:fix/decode-byte-array-errors
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+49
−1
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
4a373f5
fix(core): decode byte-array encoded API error messages
Rohan-Mohite14 0412d47
Update packages/core/src/utils/errorParsing.ts
Rohan-Mohite14 e789c4b
Update packages/core/src/utils/errorParsing.ts
Rohan-Mohite14 a37c6c9
Update packages/core/src/utils/errorParsing.ts
Rohan-Mohite14 d776f0b
Merge branch 'main' into fix/decode-byte-array-errors
Rohan-Mohite14 3a5689d
Merge branch 'main' into fix/decode-byte-array-errors
Rohan-Mohite14 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
Some comments aren't visible on the classic Files Changed page.
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
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
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.
I noticed an edge case here.
When the code successfully decodes
error.messageand recursively callsparseAndFormatApiError(decoded, ...), it passes only the new string andleaves behind the original outer object, dropping
error.status.Timeline of what happens if the API returns a 429 Error:
{ message: "78,111...", status: 429 }tryDecodeByteArraydecodes the message into the string"No capacity available".parseAndFormatApiError("No capacity available", ...)instead of an object,
statusno longer exists.if (error.status === 429)) is never reached.Actual Output:
[API Error: No capacity available]Expected Output:
[API Error: No capacity available]Please wait and try again later. To increase your limits...We should clone the error object here so we can preserve the original HTTP
status before recursing: