next.js

33cae0fe - app-render: wait for request debug stream before resolving Flight

app-render: wait for request debug stream before resolving Flight When node streams and the experimental React debug channel are both enabled, request-time Flight decoding can resolve before the debug stream has completed. In restart-on-cache-miss flows this races metadata insertion and can leave metadata tags (title/canonical) in the body fallback path instead of in head, causing use-cache metadata resume tests to time out waiting on head selectors.\n\nTrack debug stream completion in getFlightStream() and gate resolution for workUnit type 'request' until both createFromNodeStream and the debug stream are done.\n\nScope is intentionally narrow: only applies when a debug stream exists, and only for request work units. Other work unit behavior is unchanged.\n\nValidated with:\nHEADLESS=true NEXT_SKIP_ISOLATE=1 NEXT_TEST_MODE=dev __NEXT_USE_NODE_STREAMS=true __NEXT_CACHE_COMPONENTS=true __NEXT_EXPERIMENTAL_DEBUG_CHANNEL=true node_modules/.bin/jest test/e2e/app-dir/use-cache/use-cache.test.ts -t "can resume a cached generateMetadata function|can serialize parent metadata as generateMetadata argument"\n\nAlso verified the same target passes without __NEXT_EXPERIMENTAL_DEBUG_CHANNEL.