You'll notice
Useful3 Signal2
Streaming responses no longer lose the last events when a connection is closing.
What's wrong with this entry?
Anonymous. No account, no email.
What
The server-sent-events reader used to cancel mid-stream once the connection was closing, discarding events it had already read. Both of those bail-outs are gone, so those events are now parsed and dispatched.
Evidence
ephemeral_event
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.228
Two new content block types are handled instead of hitting the unknown-type path
Both mention streaming
-
v2.1.247
The
interruptible_tool_in_progressstream event is goneBoth mention streaming
-
v2.1.248
Streaming deltas can no longer crowd out task lifecycle events
Both mention streaming