fix: manage silence for new SSRC with existing user_id #2808
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
Hi Team, thanks for your amazing work, I hope this PR will find you well.
When some events occurred like leaving a voice channel or having a network interrupt, when the user join again there is a new SSRC, so the code treat that like a new user joining, so the silence is not correctly sync.
This PR aiming to change the dict key to user_id and provide the correct silence between previous and new SSRC.
Information
examples, ...).
Checklist
type: ignore
comments were used, a comment is also left explaining why.