Fix AttributeError when streaming chunk content is None #7153
+3
−1
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.
Why are these changes needed?
The console streaming renderer unconditionally appends
message.contentfromModelClientStreamingChunkEvent. In edge cases or malformed streams, this cancause an AttributeError and crash the UI.
What was changed?
Added a defensive check to ensure
message.contentis not None before appendingit to the streaming buffer. This does not change behavior for valid streaming
chunks and prevents UI crashes.
Related issue number
Fixes #7130
Checks