-
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
HTTP2: Ensure we flush when a window limit is hit #52797
Conversation
Tagging subscribers to this area: @dotnet/ncl Issue DetailsFixes #52451 When writing a request body, we need to ensure we flush if we hit a window limit (connection or stream) because we don't know when we will be able to write further data, since it depends on receiving a window update from the peer. Also, minor related test cleanup.
|
/azp run runtime-libraries-coreclr outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
@dotnet/ncl can I get a review? |
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
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
bool flush = false; | ||
if (finalFlush && remaining.Length == 0) | ||
{ | ||
flush = true; | ||
} |
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.
Nit:
bool flush = false; | |
if (finalFlush && remaining.Length == 0) | |
{ | |
flush = true; | |
} | |
bool flush = finalFlush && remaining.Length; |
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.
Other than the one pending nit, LGTM.
Fixes #52451
When writing a request body, we need to ensure we flush if we hit a window limit (connection or stream) because we don't know when we will be able to write further data, since it depends on receiving a window update from the peer.
Also, minor related test cleanup.