Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Errored fallback with an async hole is dropped inside a pending outer Loading (SSR streaming)

Abierto
  • ¿Algo no está bien?
#4,306 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript, typescript
Área
frontend

Línea de trabajo

Start with renderOutcome in packages/solid/src/server/signals.ts, then trace how the nested Errored region is handled while the outer Loading boundary is pending. Reproduce the reported timing with the three async createMemos and compare streamed and loaded hydration. Done when both hydrate with “outerfailed: no user 7 HINTtail” and no hydration warnings.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

What happens

An <Errored> whose fallback reads async data, sitting inside an outer <Loading> that is still pending, hydrates without its fallback when the inner <Loading> fails after the shell. The Errored region disappears.

<div>
  <Loading fallback={<i>outer loading</i>}>
    <b>{outer()}</b>
    <Errored fallback={e => <p>failed: {e().message} {hint()}</p>}>
      <Loading fallback={<i>loading</i>}>
        <span>user:{user()}</span>
      </Loading>
    </Errored>
  </Loading>
  <span>tail</span>
</div>

Three async createMemos are created in the component body:

  • user rejects with "no user 7" at 5ms.

  • hint resolves to "HINT" at 10ms.

  • outer resolves to "outer" at 15ms.

  • Expected: outerfailed: no user 7 HINTtail

  • Actual: outertail, with one or two hydration warnings. Both streamed and loaded hydration show this on next.

Server output

The shell has <i>outer loading</i> at pl-4. The stream rejects user, resolves hint, then sends <template id="4"><b _hk=4000>outer</b></template> and $df("4"). It sends nothing for the Errored region: no fallback markup and no inner placeholder.

Likely cause (unconfirmed)

The inner fragment is parked under the pending outer boundary. It fails while the Errored fallback's async hole is still pending, so the outcome render (renderOutcome in packages/solid/src/server/signals.ts) produces no markup. When the outer Loading later resolves, the Errored subtree is dropped instead of sending its fallback, or a placeholder the client can render into.

Found while reviewing #4303. That PR fixes the same shape without the outer Loading; this nested case fails the same way before and after it.

Generated by Claude Code

Lenguaje dominante
TypeScript
Estrellas
36.2k
Forks
1.1k
Merge medio
11 h 5 min
PR fusionados (30 d)
353

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de solidjs/solid

Todos los issues de solidjs/solid

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.