Handle unexpected json structure in error payload #95
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
|
@sfc-gh-xhuang could you arrange for the tests to run? Even in the CI workflows it appears they don't have access to the key. |
sfc-gh-yawang
approved these changes
Aug 23, 2024
|
Test successfully ran with copy PR #96 |
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.
Addresses the issue where handling any API error response that does not conform to expected JSON response raises KeyError rather providing information about the HTTP error.
Works by catching any KeyErrors and instead providing a generically informative exception message based on the one reported if there is no JSON payload.
closes: #92