Add compatibility for aliyun LLM APIs #530
Open
+3
−3
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
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.
Summary
Some Aliyun API responses do not include the
status_detailsfield, which causes an error when trying to access it. This PR ensures compatibility by settingstatus_detailstonullwhen it is missing.Changes
status_detailsexists in the response before accessing it.status_detailstonullif it is not present.Why this is needed
Without this fix, Aliyun API responses that lack
status_detailswill cause runtime errors, breaking the client integration.Testing
status_detailsis missing).Backward Compatibility
✅ Fully backward compatible. If
status_detailsis present, the behavior remains unchanged.