[test] Park the blocking-fallback segment on a withheld param (#95300)
The `blocking-fallback/[lang]/[scope]` fixture's deeper page previously rendered a static title and gated its only dynamic work on a `cookies( ` read. Under instant() the committed app shell is allowed to read reque t cookies without blocking, which is exactly what the cookie assertions n this suite rely on, so a segment gated only on cookies renders into th shell and its title commits while the lock is held. Under CPU load thi surfaced as a flaky leak of `blocking-scope-title` during the parke navigation, and instrumenting the lock's read path confirmed the cause the test failed precisely when the app-shell (RuntimeShell) entry committe the deeper segment and passed when the speculative static prefetch (PPR) e try committed, a commit-order race between the two prefetch responses This change makes `ScopePage` await `params` before rendering anything. Because `scope` is an uncovered fallback param (the route has no `generateStaticParams`), awaiting it suspends the whole segment during the app-shell prerender and keeps both the title and the cookie value out of the committed shell regardless of which prefetch wins. The segment streams in only after the lock releases, when the real dynamic render resolves `params`. The underlying app-shell-versus-speculative-prefetch race is a known, likely temporary limitation; the `cookies in the instant shell` describe block documents the related case and the planned fix of opting cookie-reading routes into partial or runtime prefetching. The test comment is updated to describe this param-gated parking instead of the previous cookie-based description. --- <sub>Stack created with <a href="https://github.com/github/gh-stack">GitHub Stacks CLI</a> • <a href="https://gh.io/stacks-feedback">Give Feedback💬 </a></sub>
Showing
Please
register
or
sign in
to comment