-
Notifications
You must be signed in to change notification settings - Fork 47.2k
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
[Flight] don't overwrite existing chunk listeners in 'wakeChunkIfInitialized' #29204
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
A bit of context: The test added in #29201 didn't go into that |
You have to change ReplyServer too whenever you change these. |
@sebmarkbage yeah, sorry about that, unfortunately we only noticed that after we merged this. @gnoff said he's gonna add that in a bit (i'm AFK r/n) |
…isteners In facebook#29201 a fix was made to ensure we don't "forget" about some listeners when handling cyclic chunks. In facebook#29204 another fix was made for a special case when the chunk already has listeners before it first resolves. This implements the followup fix for Flight Reply which was originally missed in facebook#29204 Co-Authored-by: Janka Uryga <lolzatu2@gmail.com>
…isteners (#29207) In #29201 a fix was made to ensure we don't "forget" about some listeners when handling cyclic chunks. In #29204 another fix was made for a special case when the chunk already has listeners before it first resolves. This implements the followup fix for Flight Reply which was originally missed in #29204 Co-authored-by: Janka Uryga <lolzatu2@gmail.com>
Follow-up to #29201. If a chunk had listeners attached already (e.g. because
.then
was called on the chunk returned fromcreateFromReadableStream
),wakeChunkIfInitialized
would overwrite any listeners added during chunk initialization. This caused cyclic path references within that chunk to never resolve. Fixed by merging the two arrays of listeners.