solidjs / solid / 40779596434

78%

main: 89%

push

github

fix(solid): a served rejection re-serves in its claim window's round (#4375) (#4385)

* fix(solid): a served rejection re-serves in its claim window's round (#4375)

An async memo the server answered with a rejection, read through a memo
over it whose pending state the page shows, was asked again when a
streamed boundary resumed: the reader the resume creates pulls the memo
over it on a later round than the one the rejection landed in, the pull
retries the errored node (PJ-R35), and the latched node, outside the
claim, ran its compute. A served rejection now re-serves in the round its
claim window opened in, as it does in a served pass; a write made there
(an effect's) runs in a later round and computes.

The `ssrSource !== "hybrid"` test is read once per call, which pays for
the new check.

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

* test(web): describe the #4375 harness's show shape

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

* fix(solid): inline the ssrSource checks in readSerializedOrCompute

* chore(size): re-record the #4375 hydrating scenarios over next @ 40cde2cd

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>

790 of 1084 branches covered (72.88%)

Branch coverage included in aggregate %.

2 of 2 new or added lines in 1 file covered. (100.0%)

1125 of 1355 relevant lines covered (83.03%)

29.96 hits per line