solidjs / solid / 39317651172

78%

main: 89%

push

github

fix(web): keep a streaming frame's flight origin for late-mounted consumers (#4140) (#4160)

A server component consumer that mounted while its frame response was
already streaming awaited a landing promise (and a `.then` wrapper over it)
minted at mount time with no flight origin, so attribution read the
delivery as new work begun after the preceding client wait resolved and
reported a false ASYNC_WATERFALL.

Observe tier only: the server-function client hands its response handler
`ctx.startedAt` (taken before the fetch), the frames handler carries it on
the header-time `start` chunk, the frame host records it per version and
stamps the landing promise it mints for an open flight, and the mount's
landing wrapper inherits that stamp. A re-ask after an error stays new
work. Prod output folds all of it out.


Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2

Co-authored-by: Claude <noreply@anthropic.com>

756 of 1050 branches covered (72.0%)

Branch coverage included in aggregate %.

1103 of 1347 relevant lines covered (81.89%)

27.56 hits per line