In the streaming branch of _wrap_chat.new_chat, when is_span_streaming_enabled=True, a StreamedSpan immediately registers itself as _scope.streamed_span during __init__ (via _start()). On the error path, _capture_exception(e) and span.__exit__(*exc_info) share a single with capture_internal_exceptions(): block. If _capture_exception raises (e.g. failure inside event_from_exception or capture_event), the exception is swallowed by capture_internal_exceptions and span.__exit__ is skipped. The span is never ended and _scope.streamed_span is not restored to its previous value, so any subsequent streamed span started on the same scope is incorrectly parented under the leaked chat span until the scope is torn down. Splitting the two calls into independent with capture_internal_exceptions(): blocks ensures cleanup always runs.

When is_span_streaming_enabled=True and chat_stream is used, _end_span(span) is only reachable at the end of the new_iterator() generator; if the caller breaks out of iteration early, the StreamedSpan is never ended and remains the active span on the scope indefinitely, causing all subsequent child spans in that scope to be incorrectly parented.