solidjs / solid / 40770641541

78%

main: 89%

push

github

fix(signals): an error staged on its source keeps <Errored> waiting (#4364) (#4387)

* fix(signals): an error staged on its source keeps <Errored> waiting (#4364)

An uninitialized async memo whose re-run throws from a dependency lost the
error, and Loading revealed an empty hole. The dependency's error was
staged for the commit (D-41), but a reader threw it at once: a render
effect reading a memo born staged, or the memo itself through latest().
That error reached <Errored> naming the source. The boundary's output pass
then took the source as settled, because its error was only staged, so it
dropped the source and showed the content. When the commit published the
error, every reader already held it, and nothing reached the boundary
again.

prune() now treats a staged error on an error boundary's source as
unsettled. It also inlines the one-line `unsettled` helper and restructures
the loop, so the change is -12 B minified.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2

* docs(signals): why catchStatus's cleared path needs no staged-error guard (#4364)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2

---------

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

788 of 1081 branches covered (72.9%)

Branch coverage included in aggregate %.

1124 of 1354 relevant lines covered (83.01%)

30.1 hits per line