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 8692ad9
Browse filesBrowse the repository at this point in the historyBrowse files
fix(solid): an Errored fallback failing in the shell goes to the enclosing boundary
An `<Errored>` whose fallback failed while rendering (a hole that rejects,
or a synchronous throw) for its content's error was left blank on the
server: the boundary's error handler had already marked the error handled
before rendering the fallback, so the fallback's own failure was dropped
and the pull returned `undefined`. At shell level, with no `<Loading>`,
the shell got a blank region with the errors recorded and no markup for
them; an enclosing `<Errored>` serialized its record but never drew.
The fallback's failure now passes up from the pull: an enclosing
`<Errored>` draws its fallback in place of the region, and with none the
request fails, the same for the async hole and its sync-throw twin.
Server only; client bundles are byte-identical.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2
An `<Errored>` whose fallback fails while rendering (a hole that rejects, or a synchronous throw) now passes that failure to the enclosing boundary on the server, in the shell as well as in a streamed fragment. An outer `<Errored>` draws its fallback in place of the region, and with none the request fails. Before, the region was sent blank, with the errors recorded and no markup for them.
0 commit comments