solidjs / solid / 37378133439

76%

main: 89%

push

github

fix(solid): server async-iterable memos keep by-slot flight memory (#3734) (#3804)

A <Loading> retry re-creates a component that reads its own async source.
Thenable memos find the slot's settled answer (or join its flight) by owner
id; the direct async-iterable branch skipped that memory, so a source that
hands back a fresh iterable per call (a subscriber, liveQuery()) planted a
new pending flight every pass and discovery never converged.

The iterable branch now records its first value / error / in-flight
deferred in the same slot store, and a re-creation adopts or joins it
without opening its own iterable or serializing a second channel. Frame
renders that pump the iterable into the binding ledger are unchanged.

Hand-written ssr() holes (the other half of the report) continue the
resolveIn id counter across passes, so their slot ids move each pass; that
needs a separate design call and is left open (pinned as test.fails).

Co-authored-by: Cursor <cursoragent@cursor.com>

649 of 925 branches covered (70.16%)

Branch coverage included in aggregate %.

962 of 1195 relevant lines covered (80.5%)

27.67 hits per line