-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Fix race when receiving HEADERS and RST_STREAM in rapid succession. #72932
Fix race when receiving HEADERS and RST_STREAM in rapid succession. #72932
Conversation
Tagging subscribers to this area: @dotnet/ncl Issue DetailsFixes #68373. This PR makes requests made with
|
258a0eb
to
4f0e1c1
Compare
/azp run runtime-libraries-coreclr outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
@@ -130,6 +130,19 @@ public async Task WriteFrameAsync(Frame frame, CancellationToken cancellationTok | |||
await _connectionStream.WriteAsync(writeBuffer, 0, writeBuffer.Length, cancellationToken).ConfigureAwait(false); | |||
} | |||
|
|||
public async Task WriteFramesAsync(Frame[] frames, CancellationToken cancellationToken = default) |
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 just to make the test more likely to fail without the fix, right?
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.
yes
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.
LGTM
Test failure is #72586 |
Fixes #68373.
This PR makes requests made with
HttpCompletionOption.ResponseHeadersRead
finish successfully even if we receive RST_STREAM frame after successfully receiving response headers.