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 2861ab8
Browse filesBrowse the repository at this point in the historyBrowse files
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 <[email protected]>
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 <[email protected]>
Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2
---------
Co-authored-by: Claude <[email protected]>
An uninitialized async memo whose re-run throws from a dependency now reaches the wrapping `<Errored>` (#4364). 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()`. The error reached the boundary naming that source, and the boundary's next pass took the source as settled because its error was only staged. It dropped the source and showed the content, so `Loading` revealed an empty hole that never recovered. An error staged on its source now keeps the boundary waiting until the commit publishes it.
0 commit comments