-
Notifications
You must be signed in to change notification settings - Fork 21
Add stop_transceiver/2 #55
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
Conversation
b6e0f82
to
f4cb9f6
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #55 +/- ##
==========================================
+ Coverage 89.01% 89.02% +0.01%
==========================================
Files 24 25 +1
Lines 965 1057 +92
==========================================
+ Hits 859 941 +82
- Misses 106 116 +10
Continue to review full report in Codecov by Sentry.
|
f4cb9f6
to
09c8bdd
Compare
7276db0
to
39cbf08
Compare
11cf0ce
to
72c80d6
Compare
72c80d6
to
a869034
Compare
%RTPTransceiver{mid: nil} -> | ||
false |
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.
We discussed a case when you created and immediately stopped a transceiver -- it won't be included in the initial offer and won't be removed when applying remote answer, which might be undesired.
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.
IMO this is a bug but that's also how the borwser behaves so I left the comment with a link to the issue
af84743
to
9985e40
Compare
9985e40
to
13beee9
Compare
No description provided.