Skip to content
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

bug-1892787: handle case where Bugzilla returns bad payload #6785

Merged
merged 1 commit into from
Nov 2, 2024

Conversation

willkg
Copy link
Contributor

@willkg willkg commented Nov 2, 2024

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 a BugzillaRestHTTPUnexpectedError 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.

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 a BugzillaRestHTTPUnexpectedError 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.
@willkg willkg requested a review from a team as a code owner November 2, 2024 13:19
@willkg willkg added this pull request to the merge queue Nov 2, 2024
@willkg
Copy link
Contributor Author

willkg commented Nov 2, 2024

Thank you!

Merged via the queue into main with commit 0753f8d Nov 2, 2024
1 check passed
@willkg willkg deleted the willkg-bug-1892787-bugs branch November 2, 2024 18:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants