fix: keep SSE alive past idle timeout (Safari "Connection lost")#376
Merged
tomasz-tomczyk merged 1 commit intomainfrom Apr 28, 2026
Merged
fix: keep SSE alive past idle timeout (Safari "Connection lost")#376tomasz-tomczyk merged 1 commit intomainfrom
tomasz-tomczyk merged 1 commit intomainfrom
Conversation
Send an initial `:\n\n` SSE comment so EventSource fires onopen immediately (Safari delays this until the first body byte), and add a 30s heartbeat ticker so the stream isn't closed by the server's 60s IdleTimeout. Without the heartbeat, idle SSE connections hit the IdleTimeout and Safari surfaces repeated "Could not connect to the server" errors. Chromium and Firefox auto-reconnect more silently, which is why this looked Safari- specific even though the root cause affected all browsers. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #376 +/- ##
==========================================
+ Coverage 66.55% 66.59% +0.04%
==========================================
Files 19 19
Lines 8169 8176 +7
==========================================
+ Hits 5437 5445 +8
+ Misses 2310 2309 -1
Partials 422 422
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
:\n\nSSE comment soEventSource.onopenfires immediately (Safari delays this until the first body byte).IdleTimeout.Why
Safari was surfacing repeated "Could not connect to the server" errors on the review page. Root cause was idle SSE connections hitting the server's
IdleTimeout: 60s— Chromium and Firefox auto-reconnect more silently, which is why this looked Safari-specific even though the root cause affected all browsers.Review
Test plan
TestEvents_SafariCompatasserts the initial:\n\nframe and heartbeat (withsseHeartbeatIntervalshrunk to 50ms).gofmt -l .cleangolangci-lint run ./...cleango test -race -count=1 ./...passes (46s)crit commentpropagated via SSE.🤖 Generated with Claude Code