solidjs / solid / 41170571222

78%

main: 89%

push

github

fix(signals): a memo waiting on a held flight is the hold's work at its landing (#4408, #4399) (#4510)

* fix(signals): a memo waiting on a held flight is the hold's work at its landing (#4408, #4399)

#4408 (F-6 amended 2026-10-28, D-26): `latest(m2)` showed `c1101` while
`m1:1122` of the same lane was in flight. `m1` (an async memo over a
verdict memo, no window of its own) was waiting on `m0`'s flight as the
hold's work (verdict.ts `holdWork`), but kept CONFIG_VERDICT, so `m0`'s
verdict-lane re-derive at the park re-derived it into the s lane early;
the lane was unshown when `m1:22` landed and nothing held the frame
`m0b:1100` landed into. `holdWork` now drops the verdict posture at the
wait: the memo is the hold's work until a pass of it reads a verdict
again (D-25: re-run by the write its hold holds, it reads plainly). The
recompute head could not tell: the landing settles the node before the
pass, and a lane's node is not held.

#4399 (F-9, D-25): two actions, each holding a verdict memo's write,
asked `m1:15` twice. `m1`'s pass over `m0b`'s landing re-entered its hold
at its head, then read `m0` (A's verdict lane) first and was moved into
that lane, where its read of its own hold's landing was the screen
(D-26), so it asked `m1:15` again. In `enterLane`, a pass that re-entered
the hold holding its node at its head stays that hold's work when the
verdict lane is another hold's, as it already did when it read its
hold's staging first (D-25: either read order). Its own hold's verdict
lane is its display-ahead read and it still enters that one (#4050).

Both decisions sit at the event (the wait's start in `propagateStatus`,
a verdict-lane read in `enterLane`), behind `holdWorkHook` and the lane
engine: nothing in recompute's hot path, 0 B in bundles without them.
The pins in latest-two-readers-one-ask-4393 (beside) and
latest-first-one-pass-4402 (#4399 split/value) flip from it.fails to it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
C... (continued)

790 of 1090 branches covered (72.48%)

Branch coverage included in aggregate %.

1126 of 1363 relevant lines covered (82.61%)

29.75 hits per line