-
Notifications
You must be signed in to change notification settings - Fork 10.3k
[release/6.0] HTTP/3: Use new QuicStream.ReadsCompleted property in transport #35476
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
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.
Does the Http/3 layer need any adjustments, or should that just work?
HTTP/3 layer will just work. It is already using the aspnetcore/src/Servers/Kestrel/Core/src/Internal/Http3/Http3Stream.cs Lines 428 to 434 in 6350af9
|
@@ -240,12 +263,23 @@ private async Task DoReceive() | |||
finally | |||
{ | |||
// If Shutdown() has already bee called, assume that was the reason ProcessReceives() exited. |
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.
not new code, but typo: "bee" -> "been"
/backport to main |
Started backporting to main: https://github.com/dotnet/aspnetcore/actions/runs/1145307320 |
/backport to release/6.0-rc1 |
Started backporting to release/6.0-rc1: https://github.com/dotnet/aspnetcore/actions/runs/1145308311 |
Closing this PR and have changes be merged from RC1 into back into 6.0 automatically. |
Fixes #35399 Made this change in this branch first because main hasn't gotten latest runtime bits yet.