Uh oh!
There was an error while loading. Please reload this page.
[release/7.0] Fix ConnectAsync with buffer on Windows - #79866
Conversation
ghost
commented
Dec 20, 2022
Tagging subscribers to this area: @dotnet/ncl Issue DetailsBackport of #79669 to release/7.0 /cc @antonfirsov Customer ImpactTestingRiskIMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.
|
carlossanlop
commented
Jan 5, 2023
Approved by Tactics (7.0.3). |
Backport of #79669 to release/7.0
/cc @antonfirsov
Fixes#79654.
Customer Impact
On Windows it's possible to send an initial buffer during
ConnectAsyncviaSocketAsyncEventArgs.SetBuffer(), which regressed in 7.0, making such connection attempts to fail.Testing
The PR adds a test case for the scenario.
Risk
Very low, we are combining the old behavior with the new pinning mechanism.