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
fix(server): streamableHttp stores request-related events when stream is disconnected
The standalone-SSE path stores to eventStore first, then writes if connected.
The request-related path only stored when the stream was live, so a
notification sent after closeSSE() (SEP-1699 polling) was silently dropped
instead of being persisted for replay on reconnect.
Exposed by the ctx.mcpReq.log request-related change against the new
sse-polling example story; the gap pre-exists on main for any
request-related notification (progress, ctx.mcpReq.notify) emitted after
closeSSE().
`WebStandardStreamableHTTPServerTransport`: request-related events (progress, `ctx.mcpReq.notify`, handler-emitted log) and the final response sent while the per-request SSE stream is intentionally closed (e.g. after `closeSSE()` for SEP-1699 polling) are now persisted to the configured `eventStore` so they replay on reconnect, and the final response no longer surfaces a spurious "No connection established" send error. Previously they were silently dropped. Events sent after a hard client disconnect (the per-request stream cancelled by the client) are not persisted.
0 commit comments