-
Notifications
You must be signed in to change notification settings - Fork 300
Reconcile the participant roster after a signal resume #2096
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
1egoman
wants to merge
5
commits into
main
Choose a base branch
from
fix/clt-3323-resume-roster-reconciliation
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.
+184
−7
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
6ecb030
test(e2ee): replay the participant roster in signal-resume simulations
1egoman e3cb14f
fix(room): reconcile the participant roster after a signal resume
1egoman ba4a5a9
test(room): cover stale participant removal after a signal resume
1egoman c5f1a50
test(room): guard the resume reconciliation against over-eviction
1egoman 4deb05b
chore: add changeset for resume roster reconciliation
1egoman 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| 'livekit-client': patch | ||
| --- | ||
|
|
||
| Reconcile the participant roster after a signal resume, removing remote participants that left while the signal connection was down |
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
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.
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.
🔴 Legacy resumes evict every participant
When an older server omits the roster replay,
resumeSeenIdentitiesstays empty and disconnects every remote participant. Active tracks and application state disappear while those participants remain.Learn more
A signal resume starts an empty identity set unconditionally. Older LiveKit servers can complete the same resume protocol without sending a full participant update, so an empty set cannot distinguish an empty room from a missing snapshot. The
Resumedhandler then treats every existing participant as absent and invokes reconcileParticipantsAfterResume, which unpublishes their tracks and emits disconnect events.Example: Alice and Bob are connected through a server that does not replay participant updates after resume. A brief signal outage completes successfully, but the set remains empty. Alice's SDK disconnects Bob locally even though Bob never left.
Recommended fix: Gate reconciliation on a server capability or minimum server version that guarantees roster replay. If no reliable version boundary exists, add an explicit snapshot-complete signal or carry the authoritative roster in the reconnect response; do not interpret the absence of participant updates as an empty roster.
Was this helpful? React with 👍 or 👎 to provide feedback.
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.
This is a good point, I wonder if (since it sounds like this was a behavior change) this needs to be gated on the SFU version? Or applied wholesale for all SFUs irrespective of version?