Skip to content

fix(flows): keep one event id across the chunks of a streamed reply - #1769

Open
copybara-service[bot] wants to merge 1 commit into
mainfrom
test_1008912735
Open

copybara-service[bot] wants to merge 1 commit into
mainfrom
test_1008912735

Conversation

@copybara-service

@copybara-service copybara-service Bot commented Nov 5, 2026 •

Copy link
Copy Markdown

fix(flows): keep one event id across the chunks of a streamed reply

  • Partial events now carry the id of the complete event that ends their reply,
    so ids repeat within a stream. A client that keys events by id should replace
    the reply's row on each chunk.
  • Tool responses keep the ids their execute_tool trace spans record, and the
    last reply of each model call carries the event id its call_llm span
    records.

@copybara-service
copybara-service Bot force-pushed the test_1008912735 branch 2 times, most recently from ef8e0ae to ef9d8e6 Compare November 6, 2026 09:04
- Partial events now carry the id of the complete event that ends their reply,
  so ids repeat within a stream. A client that keys events by id should replace
  the reply's row on each chunk.
- Tool responses keep the ids their `execute_tool` trace spans record, and the
  last reply of each model call carries the event id its `call_llm` span
  records.

PiperOrigin-RevId: 1008912735
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant