Uh oh!
There was an error while loading. Please reload this page.
Do not flush serializer buffers before first IAsyncEnumerable element is fetched - #59808
Conversation
ghost
commented
Sep 30, 2021
Tagging subscribers to this area: @dotnet/area-system-text-json Issue DetailsAddresses dotnet/aspnetcore#36977 See dotnet/aspnetcore#36977 (comment) for an explanation of the issue. Should consider servicing in 6.0
|
eiriktsarpalis
commented
Sep 30, 2021
pranavkm
commented
Sep 30, 2021
Nice. FYI @BrennanConroy since this would resolve the IAsyncEnumerable issue. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
steveharter
left a comment
There was a problem hiding this comment.
The strategy of deferring the first flush is sound; a couple questions around Asserts
ericstj
commented
Oct 1, 2021
|
eiriktsarpalis
commented
Oct 1, 2021
/backport to release/6.0 |
Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/1295615263 |
Addresses dotnet/aspnetcore#36977
See dotnet/aspnetcore#36977 (comment) for an explanation of the issue.
I ran the benchmark suite against the changes and no performance regression was recorded.
Should consider servicing in 6.0.