Repository navigation
[Fizz] Detatch boundary after flushing segment with boundary - #34694
Merged
Merged
Conversation
gnoff
force-pushed
the
detatch-boundary-after-flush
branch
from
October 2, 2025 19:23
66754f3 to
693513a
Compare
sebmarkbage
approved these changes
Oct 2, 2025
When we flush a Suspense boundary we might not flush the fallbak segment, it might only flush a placeholder instead. In this case the segment can flush again but we do not want to flush the boundary itself a second time. We now detatch the boundary after flushing it.
gnoff
force-pushed
the
detatch-boundary-after-flush
branch
from
October 2, 2025 19:24
693513a to
2eeb068
Compare
|
Comparing: c825f03...2eeb068 Critical size changesIncludes critical production bundles, as well as any change greater than 2%:
Significant size changesIncludes any change greater than 0.2%: (No significant changes) |
github-actions Bot
pushed a commit
that referenced
this pull request
Oct 2, 2025
When we flush a Suspense boundary we might not flush the fallback segment, it might only flush a placeholder instead. In this case the segment can flush again but we do not want to flush the boundary itself a second time. We now detach the boundary after flushing it. better solution to: #34668 DiffTrain build for [7d9f876](7d9f876)
This was referenced Oct 3, 2025
buidangphuc
added a commit
to buidangphuc/agora
that referenced
this pull request
Nov 5, 2026
…ush bug E2e scenario "The page streams to the end whatever the description length" (40 listings, descriptions of 1-40 chars, each PDP must end in </html> and include #qa) and a vitest of the upstream React regression case (react/react#34694) on Next's vendored react-dom/server. OpenSpec change pdp-stream-cutoff. Red on Next 15.5.28's vendored React (7-18 char descriptions cut at ~121 KB; the vitest reports the invariant). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
buidangphuc
added a commit
to buidangphuc/agora
that referenced
this pull request
Nov 5, 2026
…r cuts off The buyer PDP stopped streaming for some page sizes: the React server renderer vendored by Next 15.5.28 flushed the AI review summary boundary twice when its fallback segment was still suspended and threw "A previously unvisited boundary must have exactly one root segment" (react/react#34668). scripts/patch-react-dom-boundary.mjs backports the upstream one-line fix (react/react#34694) into every vendored Fizz bundle during dev and build, and exits 1 when Next changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When we flush a Suspense boundary we might not flush the fallback segment, it might only flush a placeholder instead. In this case the segment can flush again but we do not want to flush the boundary itself a second time. We now detach the boundary after flushing it.
better solution to: #34668