-
Notifications
You must be signed in to change notification settings - Fork 10.5k
HTTP/3: Complete outbound control stream with connection #33956
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
|
|
||
| lock (_sync) | ||
| { | ||
| OutboundControlStream?.Abort(connectionError, (Http3ErrorCode)_errorCodeFeature.Error); |
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.
Is the lock really necessary? If we see a stale null OutboundControlStream, is it wrong to treat it as if it hadn't been fully created? I know this lock was there before and it doesn't really hurt if it's generally uncontested. I'm just curious.
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.
It's probably not necessary. Can look at cleaning it up in the future.
|
Hello @JamesNK! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
|
/azp build |
|
Command 'build' is not supported by Azure Pipelines. Supported commands
See additional documentation. |
|
/asp run |
0fa84bc to
77fb3af
Compare
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
Ensure that the outbound control stream is completed when the connection is completed.
(right now it is completed via Stream.Abort, future issue will cover graceful shutdown)