-
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
[RSDK-8666] Use Stoppable Workers #408
Changes from all commits
5a92489
99c5ece
c8a02cf
80eb5df
2fd4869
7a7b604
b59f413
7a86540
e57158a
642c943
d46bd50
0b5c310
41309b6
54731bc
20566aa
b2d328c
fe3a863
d29f0e8
fac6086
ba8ce89
297739d
2dc6cc5
58458a9
c2a4c08
fcf72dd
8fd687a
3a5e3c7
cc4887d
d6d8aa2
ef5b3d3
657a560
31001ec
454d29f
b203203
8a66f53
0840eba
7eb91ef
6a5d752
8241b32
16e2f4b
ae45b2b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -37,7 +37,7 @@ func newWebRTCServerChannel( | |
logger utils.ZapCompatibleLogger, | ||
) *webrtcServerChannel { | ||
base := newBaseChannel( | ||
server.ctx, | ||
server.processHeadersWorkers.Context(), | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. An artifact of no longer storing a There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Gotcha; this makes sense to me. There's a hierarchy here of WebRTC server owns WebRTC server channels owns WebRTC server streams. We want the context cancelations to propagate in that order. So, I think what you have here is correct. Once There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Agreed this will do the right thing. It would be more customary to just have |
||
peerConn, | ||
dataChannel, | ||
func() { server.removePeer(peerConn) }, | ||
|
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 no longer the same context. Before this
ctx
was the one passed intoSendOfferInit
. Now we've shadowed that with theactiveBackgroundWorkers
context. Which is already covered by thesendCtx
.Taking a step back. In the existing code, I'm not sure what the relationship is between the caller's context and the
queue.cancelCtx
. I think* theSendOfferInit
ctx
is the gRPC request's context. In which case we'd want to revert to using that one.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.
nice catch totally missed this