You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b8af6b9
Browse filesBrowse the repository at this point in the historyBrowse files
fix(signals): a derivation of a staged error re-runs instead of carrying it
D-41: a derivation that reads a staged error throws it, as it would read
a staged value: its own pass errors and stages with the same frame. The
earlier change marked every derivation under a staged error with that
error without running it, so a memo or derived-store derive that catches
the error showed an error it never threw for the whole hold, and a
derived store's keys that never read the source threw it too (D-30). Read
only through latest(), both ended errored after the commit.
The settle walk now re-runs those derivations; a pass that catches
answers with its own value. A boundary's output and tree, async memos,
effects and nodes that own children (a boundary's content, #3945) are
left to the commit's publish as before. A projection's derive stages its
pass's error like a memo. A published error no longer marks a node that
holds its own pass's answer to the frame, which also fixes a catching
memo ending errored when the error's flush has no hold.
The silent-recovery pin counts the dependent's own errored pass.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2
Copy file name to clipboardExpand all lines: .changeset/staged-error-reaches-derivations.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,4 +2,4 @@
2
2
"@solidjs/signals": patch
3
3
---
4
4
5
-
A memo's error staged with a hold now reaches the memos and derived stores that derive from it: `latest()` of them throws the proposed error and `isPending()` of them is `true` until the hold commits, as for the memo itself (D-41).
5
+
A memo's error staged with a hold now reaches the memos and derived stores that derive from it: they re-run against it, so `latest()` of them throws the proposed error and `isPending()` of them is `true` until the hold commits, as for the memo itself (D-41). A memo or derived-store derive that catches the error answers with its own value instead, during the hold and after it: it no longer ends errored with an error its pass never threw, and a derived store's other keys keep their values (D-30).
0 commit comments