fix(ai-proxy): check type of choices/usage/content fields before use it#12548
Merged
Revolyssup merged 4 commits intoAug 28, 2025
Merged
Conversation
dosubot
Bot
added
size:M
nic-6443
reviewed
Aug 28, 2025
nic-6443
approved these changes
Aug 28, 2025
Contributor
Author
|
failing test unrelated and flaky |
nic-chen
approved these changes
Aug 28, 2025
AlinsRan
approved these changes
Aug 28, 2025
jizhuozhi
pushed a commit
to jizhuozhi/apisix
that referenced
this pull request
Oct 18, 2025
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
4 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.
In the user's environment, the content field returned by the LLM service may be null. Our code needs to handle this case to avoid panic:
Checklist