Uh oh!
There was an error while loading. Please reload this page.
only slice SocketAddress on success operation - #90284
Conversation
ghost
commented
Aug 10, 2023
Tagging subscribers to this area: @dotnet/ncl Issue DetailsThis is regression from #88970. Change is UpdateReceivedSocketAddress is small cleanup as we do not need to special case it any more. fixes #90125
|
wfurt
commented
Aug 10, 2023
/azp run runtime-libraries-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
wfurt
commented
Aug 10, 2023
/azp run runtime-libraries-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
wfurt
commented
Aug 10, 2023
/azp run runtime-libraries-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
wfurt
commented
Aug 10, 2023
/azp run runtime-libraries-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
wfurt
commented
Aug 11, 2023
outerloop test failures are unrelated. |
This is regression from #88970.
When the SocketPal.TryCompleteReceiveFrom fails e.g. no data yet, we should not Slice the SocketAddress because on next round we would not have buffer to receive to. (as we do in case just bellow)
This was added to avoid tracking SocketAddressLength as separate parameter.
Change is UpdateReceivedSocketAddress is small cleanup as we do not need to special case it any more.
fixes#90125