fix BlazarClientException ignoring status code#44
Merged
msherman64 merged 1 commit intochameleoncloud/2023.1from Nov 5, 2025
Merged
fix BlazarClientException ignoring status code#44msherman64 merged 1 commit intochameleoncloud/2023.1from
msherman64 merged 1 commit intochameleoncloud/2023.1from
Conversation
the base BlazarClientException class was never setting "self.code", even when passed as an argument. This led to any http exception, including 404, being reported as a 500 error.
Mark-Powers
approved these changes
Oct 31, 2025
Mark-Powers
left a comment
There was a problem hiding this comment.
This looks correct. I know there used to be issues on the API side where the status code was not overriden for some exceptions.
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
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.
the base BlazarClientException class was never setting "self.code", even when passed as an argument. This led to any http exception, including 404, being reported as a 500 error.