solidjs / solid / 40860831099

78%

main: 89%

push

github

fix(signals): an Errored boundary recovers instead of looping when its memo is re-asked (#4403, #4404, #4405) (#4406)

A root <Errored> on its fallback waits on the source that threw (D-39).
The seam drops a source it judges settled and redraws, and the output's
pass re-catches the tree's error without re-running it. Each shape left
the tree carrying an error the graph would never re-derive, so the redraw
re-caught it every round ("Potential Infinite Loop Detected").

- #4404 (D-41: a derivation that reads a staged error throws it): a reader
  born in the flush read the committed error of a memo whose new error was
  staged; its stale error committed after the new one. `read` now serves
  such a reader the staging (`serve`), as it would a staged value.
- #4403 (D-41: a recovery equal to the last good value is a change): a pass
  replacing an error the memo had staged (with a hold it joined, D-8) was
  judged unchanged when it computed the committed value, so the `latest()`
  readers that threw the staged error kept it. Such a pass is now a change.
- #4405 (D-3: structure reads the screen and re-derives at the commit;
  D-39): `reruns` skipped a boundary tree errored at the landing of the
  action that remounted its content, so it never linked the new content
  whose recovery had to reach it. Boundary structure now re-derives there.


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

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

790 of 1084 branches covered (72.88%)

Branch coverage included in aggregate %.

1125 of 1355 relevant lines covered (83.03%)

30.1 hits per line