You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit dc2a2b4
Browse filesBrowse the repository at this point in the historyBrowse files
fix(ai): record mid-stream errors on streamed OpenAI, Anthropic and Gemini events (#1094)
* fix(ai): record mid-stream errors on streamed OpenAI, Anthropic and Gemini events
capture_streaming_event hard-coded $ai_http_status=200, and the stream
generators only had a finally block. When the provider stream raised after
the first chunk (overloaded, connection reset), the event was sent as a
success with no $ai_is_error/$ai_error, unlike the non-streaming path.
Catch the exception in each sync and async generator, pass it through
StreamingEventData, and re-raise unchanged. The event now carries
$ai_is_error, $ai_error and the error's status code (0 when it has none).
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(ai): pass the stream error to StreamingEventData directly and update the API snapshot
mypy 1.16 rejected splatting {"error": error} into StreamingEventData(...)
(typeddict-item). The field accepts None and capture_streaming_event reads it
with .get(), so pass error=error. Regenerate the public API snapshot for the new
StreamingEventData.error field.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
Streamed OpenAI, Anthropic and Gemini generations that raise mid-stream are now captured with `$ai_is_error` and `$ai_error` (and the error's status code as `$ai_http_status`) instead of being recorded as a successful 200. The error is still re-raised to the caller, matching what non-streaming calls already did.
0 commit comments