-
Notifications
You must be signed in to change notification settings - Fork 2k
Fix WebSocket transcription disconnects — 64K Sentry events (#6193) #6201
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
13 commits
Select commit
Hold shift + click to select a range
0beacc1
fix(desktop): robust WebSocket reconnection in TranscriptionService
beastoin b5e98ec
fix(desktop): graceful WebSocket close forwarding in proxy
beastoin 910dee2
docs(desktop): changelog entry for WebSocket reconnect fix
beastoin 3c2e572
fix(desktop): address review — gate auth on generation, idempotent di…
beastoin 15ebfe4
fix(desktop): bump generation on teardown, salvage partial audio buffer
beastoin 265a533
fix(desktop): re-buffer unsent chunks on replay failure
beastoin 7961fb8
refactor(desktop): expose ring buffer and backoff for testability
beastoin 92ef102
test(desktop): add unit tests for ring buffer and backoff calculation
beastoin 211ef38
fix(desktop): update OnboardingFlowTests for new migratedStep params
beastoin 1a4befd
fix(desktop): update OnboardingFlowTests for current 17-step flow
beastoin e4c2ef0
fix(desktop): unwind state on invalid URL, sequential replay to preve…
beastoin 6c2f8be
refactor(desktop): add test accessors for state machine verification
beastoin d98b3fd
test(desktop): add state machine, idempotency, and URL construction t…
beastoin 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
Oops, something went wrong.
Oops, something went wrong.
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.
upstream_sink.close()forClientClosedWhen the client sends a
Closeframe,upstream_sink.close()is already awaited here before returningProxyCloseOrigin::ClientClosed. Then in the post-select!match block (lines 285–287),upstream_sink.close()is called a second time via the timeout wrapper.The second call is typically harmless (the sink ignores a redundant close), but it is redundant and adds an unnecessary 5-second timeout wait for a connection that's already cleanly closed.
One way to avoid this is to skip the inner
upstream_sink.close()and let the outer match block handle all close forwarding uniformly:This makes the post-
select!block the single authoritative place for close forwarding.