Why: A dropped subscription had no retry hint, and a reconnect had no test that the gap is filled.
Evidence: The stream starts with retry: 1000. Last-Event-ID after overflow replays the missed events.
Impact: EventSource waits one second before reconnecting.
Refs: feature/runstate-shell
Why: A dropped subscription had no retry hint, and a reconnect had no test that the gap is filled.
Evidence: The stream starts with retry: 1000. Last-Event-ID after overflow replays the missed events.
Impact: EventSource waits one second before reconnecting.
Refs: feature/runstate-shell
Why: A dropped subscription had no retry hint, and a reconnect had no test that the gap is filled from the cursor.
Evidence: The stream starts with retry: 1000. A live publish is delivered, and Last-Event-ID after an overflow replay skips events the client already has.
Impact: EventSource waits one second before reconnecting. Persisted events are unchanged.
Refs: feature/runstate-shell
Co-authored-by: Cursor <cursoragent@cursor.com>
weichen
merged commit 8f946e3094 into main2026-10-03 16:41:40 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why: A dropped subscription had no retry hint, and a reconnect had no test that the gap is filled.
Evidence: The stream starts with retry: 1000. Last-Event-ID after overflow replays the missed events.
Impact: EventSource waits one second before reconnecting.
Refs: feature/runstate-shell