solidjs / solid / 33417377779

72%

main: 89%

push

github

fix: close superseded async-iterable flights at supersede time (#3122)

The iterator close was registered only as an owner cleanup, and a
recompute whose previous-run disposal rides the zombie-deferred channel
drains it at commitPendingNode — which a verdict-held write defers
until the SUPERSEDING flight settles, so the stale iterator ran to
completion (its landing discarded by flight identity) and return()
fired only after the new answer arrived. Iterator close is the
cancellation hook for anything resource-shaped behind a stream, so a
_flightTeardown slot on the extension now fires at recompute's
_inFlight release, keyed to flight identity; the owner-cleanup
registration stays as the death backstop (close is idempotent).
Conscious treeshake-floor bump: +96B, measured 21,331.

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

517 of 789 branches covered (65.53%)

Branch coverage included in aggregate %.

767 of 1003 relevant lines covered (76.47%)

14.54 hits per line