bug-1892787: handle case where Bugzilla returns bad payload #6785
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.
Sometimes Bugzilla returns an HTTP 200 with JSON content, but it doesn't have "bugs" in it.
Rather than throw an HTTP 500 because of an unhandled
KeyError
, this changes the code to raise aBugzillaRestHTTPUnexpectedError
with the payload it did get. This will give us a better idea of what's happening so we can figure out what to do about it if anything.