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

[2.0 / next] Outside latest reads of a derivation expose errors and values at different times

Abierto
  • ¿Algo no está bien?
#4,106 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
22/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 the publication rules in packages/signals/docs/RULES-DERIVED.md, specifically D-22 and D-41, then reproduce in the playground steps listed in the issue. Compare how latest(derived) publishes a fulfilled value versus a rejected one while a sibling is pending, since the two paths currently diverge. Done means both outcomes become visible at the same point, with the held-frame behaviour matching the async sibling case. Design choices here are contested, so confirm the intended rule with maintainers before changing code.

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

Descripción

Describe the bug

With derived = createMemo(() => latest(source)), outside reads of latest(derived) expose successful and failed outcomes at different points during a held update.

A successful result becomes readable before the frame reveals. A rejection only becomes observable through the derivation after reveal, even though direct latest(source) already throws it. An async sibling keeps the frame held in both cases.

Your Example Website or App

https://s.olid.uk/id/Bp_ILv8vREiTHbnn0x6Ppg

Steps to Reproduce the Bug or Issue

Wait for Derived effect: 1 and Committed round: 1. The Read latest button samples both accessors from an event handler, outside a reactive computation.

Rejected result:

  1. Click Start update, then Reject source.
  2. Click Read latest. The output shows latest(source): boom but latest(derived): 1. The read helper catches thrown errors and displays their messages. The committed round remains 1 because the sibling is still pending.
  3. Click Release sibling, then Read latest again. Both reads now throw boom, and the committed round is 2.

Successful result:

  1. Reload the playground.
  2. Click Start update, then Resolve source to 2 (control).
  3. Click Read latest before releasing the sibling. Both reads already return 2, while the committed round remains 1.
Expected behavior

Outside reads should follow a consistent publication rule for successful and failed outcomes.

The point at which latest(derived) exposes a new outcome should not depend on whether the source fulfills or rejects.

Screenshots or Videos

No response

Platform
  • OS: Linux
  • Browser: Chromium 154.0.8037.57
  • Solid: playground pinned to the next build at d5e32a9af41c7bfe0bc090f7438ee4297d540b17, which includes #4085.
Additional context

Related to #4085. Both the rejection and fulfillment paths were verified in the hosted playground.

The related publication rules are D-22 and D-41.

Lenguaje dominante
TypeScript
Estrellas
36.1k
Forks
1.1k
Merge medio
11 h 32 min
PR fusionados (30 d)
356

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.