fix: include the server error message in raise_for_status HTTP errors - #181
Merged
Merged
Conversation
Previously only 400 responses surfaced the server's error message; other statuses raised a bare "409 Client Error: CONFLICT for url" style message, hiding the actual rejection reason from CLI users and logs. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
GonBogner
force-pushed
the
fix/TKT-17943-surface-server-error-message
branch
from
August 24, 2026 11:56
b59e945 to
88fb424
Compare
GonBogner
changed the title
or-saiag-eliezer
approved these changes
Aug 24, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Generated description
Below is a concise technical summary of the changes proposed in this PR:
Propagate server-provided error messages through
raise_for_statusso offline scan uploads reveal the actual rejection reason, such as an unsupported Windows scanner version, instead of a generic HTTP error. Update the SDK version and validate the behavior with a conflict-response test.Latest Contributors(2)