Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#4,106 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
22/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript, typescript
Ambito
frontend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
TypeScript
Stelle
36.1k
Fork
1.1k
Merge medio
11h 32m
PR unite (30g)
356

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di solidjs/solid

Tutte le issue di solidjs/solid

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.