-
Notifications
You must be signed in to change notification settings - Fork 46
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
Use pion/webrtc/v4 #370
Use pion/webrtc/v4 #370
Conversation
Test failure unrelated |
All of the changes you made in the v3 branch for us are in the v4 branch? Particularly the ones that weren't included in the old v3 branch because they were deemed backwards breaking? I think the main one being the rtp passthrough related change where OnTrackReceived will be called once the SDP is renegotiated (as opposed to also requiring the first packet to be sent). |
Yeah that RTP one would still need to be addressed here. Everything else in the fork is present in v4. |
I'm offering up pion/webrtc#2933 to see if we can get it in without simulcast changes (that viam doesn't use). |
@dgottlieb I got the OnTrack bit in as a setting |
} | ||
|
||
func (ch *webrtcBaseChannel) onChannelError(err error) { | ||
if errors.Is(err, sctp.ErrResetPacketInStateNotExist) || | ||
isUserInitiatedAbortChunkErr(err) { | ||
ch.onChannelClose() |
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.
@dgottlieb this plus a few lines above ends up fixing a case where some tests don't see the channel close with an error "in time"
@dgottlieb do you think we should move forward with this or abandon? |
Oops, I missed this update. That changes the calculus. Just to prepare for how painful this is to propagate/rollback: we really only have to change this repo + rdk? I think |
Yeah it'll be easy to revert. And yes for app too, shouldn't matter. |
This reverts commit 3452a58.
I'd suggest moving to v4 since v3 is no longer supported.