-
Notifications
You must be signed in to change notification settings - Fork 48.4k
[Flight] Prevent serialized size leaking across requests #33121
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
You should remove it from emitChunk and add it around |
I thought that was intentionally around |
emitChunk can't be recursive can it? |
You can repro that in the Flight fixture. |
But it's still around |
f220f7e
to
9aeea74
Compare
Summary
Follow-up to #33030. We end up not starting with
emitChunk
when we retry deferred text and therefore didn't stash and restore the initial size.Now we stash and restore in
retryTask
as well to cover that case.tryStreamTask
immediately goes intoemitChunk
which already takes care of stash+restore.How did you test this change?
serializedSize
value across requests in flight fixture (we ended up leaking 13 for each request i.e.deferred text
.length)