Repository navigation
rtc: close the room when Room.connect is cancelled #813
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
Open
ubmids
wants to merge
3
commits into
livekit:main
Choose a base branch
from
ubmids:fix/connect-cancellation
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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
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.
connect()does not wait for_aborted_connect_tasks, so a retry on the sameRoomcan race the still-in-flight join from the cancelled attempt.Scenario:
await asyncio.wait_for(room.connect(url, token), 0.2)in a retry loop, with nodisconnect()between attempts. Attempt 2 joins, then attempt 1's FFI join completes with the same identity. The server evicts attempt 2 as DUPLICATE_IDENTITY, and the cleanup then closes attempt 1. The caller is left with a dead room, which is the #804 symptom again.The retry numbers in the description were measured with a
disconnect()between attempts, so this path is not covered. Awaiting the same shielded gather at the top ofconnect()closes the race. A test for retry-on-the-same-Room-without-disconnect would also be good.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.
Good catch. connect() now awaits the same shielded gather before it joins (
_wait_aborted_connects(), shared withdisconnect()). Addedtest_a_retry_on_the_same_room_waits_for_the_cancelled_attempt, which fails on the previous head. Live against livekit-server 1.13.7:wait_for(connect, 0.02)then a retry on the same Room with no disconnect, 10 trials. Previous head: 3 of 10 retries never completed (10 s timeout). Now: 10 of 10 connected and still connected 3 s later.