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 5bb98aa
Browse filesBrowse the repository at this point in the historyBrowse files
fix(events): start every SSE response once its subscriptions are live
Next sends a route's status and headers with the first body chunk, and
createSSEStream wrote nothing until an event or the 30 s heartbeat. A client
therefore saw no response for up to 30 s after connecting: the desktop inbox
doorbell E2E waited 32-34 s for its stream to open in every run, and Sim
desktop's doorbell gives up on a response that has not started within 15 s.
- createSSEStream writes a `: connected` comment as soon as every
subscription is live, which starts the response at once.
- PubSubChannel exposes ready(), settled when the process's Redis SUBSCRIBE
completes, so a client that reads its state on open cannot miss an event
published before the channel was listening. The desktop doorbell, chat
status and MCP streams wait on their channels.
- The desktop inbox E2E asserts the doorbell opens within the desktop's 15 s
handshake and that a ring arrives within 2 s of the open.
0 commit comments