Improve error response handling #386
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
Instead of panic'ing when an error response cannot be decoded from JSON, return a generic error which includes the read portion of the response body. Followup to @dgryski's comment: #367 (comment)
dgryski
requested changes
Nov 15, 2022
dgryski
requested changes
Nov 15, 2022
Provide context for why the response's body is included in the error message and the decode error is not.
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.
Instead of
panic'ing when an error response cannot be decoded from JSON, return a generic error which includes the read portion of the response body.Followup to @dgryski's comment: #367 (comment)