-
Notifications
You must be signed in to change notification settings - Fork 0
fix: auto-upgrade HTTP to WebSocket for header subscriptions #36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
e2dfe69
fix: auto-upgrade HTTP to WebSocket for header subscriptions
tac0turtle cfa89fa
fix: close previous WS client on re-subscription to prevent leak
tac0turtle 81403e6
fix: use goroutine+timeout for WS dial to avoid context leak
tac0turtle 660006e
feat: add periodic streaming progress log and fix WS dial context
tac0turtle 430e9ae
docs: document poll fallback gap-skipping behavior
tac0turtle File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WS connection leaks when the dial-timeout fires but the goroutine subsequently succeeds.
doneis achan wsSubscribeResultof capacity 1. Whentime.After(wsDialTimeout)fires andsubscribeViaWSreturns an error (falling back to polling), the goroutine is still alive with the parentctx. If it later manages to dial and subscribe it writes{ch: ch, closer: closer}into the now-unread buffer. Nobody drainsdoneafter the timeout branch exits, so:closeris never called — the WS client stays open untilctxends.chruns indefinitely with no consumer.🛡️ Proposed fix: drain and close in a background goroutine on timeout
select { case r := <-done: if r.err != nil { return nil, r.err } f.mu.Lock() old := f.subCloser f.subCloser = r.closer f.mu.Unlock() if old != nil { old() } return r.ch, nil case <-time.After(wsDialTimeout): + // Drain the channel in the background and clean up if the goroutine + // eventually succeeds, to avoid leaking the WS connection/subscription. + go func() { + if r := <-done; r.closer != nil { + r.closer() + } + }() return nil, fmt.Errorf("WS connection to %s timed out after %s", wsAddr, wsDialTimeout) case <-ctx.Done(): return nil, ctx.Err() }🤖 Prompt for AI Agents