chore: ignore not-initialized calls when calculating media session state#40867
Conversation
|
Looks like this PR is ready to merge! 🎉 |
|
WalkthroughThe PR converts ChangesCall Initialization State Management
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested labels
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Warning Review ran into problems🔥 ProblemsErrors were encountered while retrieving linked issues. Errors (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #40867 +/- ##
=========================================
Coverage 70.12% 70.12%
=========================================
Files 3341 3341
Lines 123558 123661 +103
Branches 22136 22193 +57
=========================================
+ Hits 86642 86717 +75
- Misses 33567 33587 +20
- Partials 3349 3357 +8
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Proposed changes (including videos or screenshots)
The client instantiates a Call object whenever a signal is received with a callId it doesn't recognize, but that Call instance only becomes valid once a "new call" signal is received. If the new signal is never received, the call remains there, blocking the media session from initializing new calls.
With this change, calls that have not been initialized yet will be ignored by the session.
This is a bug on the lib, but there's no easy way to trigger this as a bug on the product as a whole.
Issue(s)
Derived from DMV-53
Steps to test or reproduce
Further comments
Summary by CodeRabbit
Bug Fixes
Refactor