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 9789498
Browse filesBrowse the repository at this point in the historyBrowse files
fix(signals): an async memo with no verdict window of its own takes no verdict role
#4397 review: with two verdict sources (`m1 = ask(1 + m0() + m0b())` over
`m0 = ask(1 + latest(s) + s())` and `m0b = ask(10 * (latest(t) + t()))`),
the grouped `[isPending(m1), m1()]` reader asked `m1:5` a second time on
stale inputs after both sources landed. m1 lost CONFIG_VERDICT when its
first source went pending, but a pass that threw NotReady at that
source's read picked it back up (F-6, `read`). The settle walk then
re-ran m1 as a verdict reader, and the committed values a hold had moved
past were served to it (A10).
The demotion is now per pass, in `recompute`. An async memo (new
CONFIG_ASYNC: its last answering pass registered a flight) whose pass
opened no isPending/latest window of its own (REACTIVE_WINDOW) does not
become a verdict reader by reading a verdict memo. It waits on its
sources like any derivation (F-9), reads them plainly (D-25), and asks
each question once. The side-effecting clear in `propagateStatus` is
gone, since that path no longer sees such a memo as a verdict reader.
Pinned: two verdict memos into one async memo, grouped and split, with
no question asked twice and equal final screens. A `test.fails` pin
records that the grouped shape still skips the t lane's m1:15/m1:16
asks that split makes: whether a later write merges into an open
transaction or opens its own lane depends on grouping (#4398).
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2
Copy file name to clipboardExpand all lines: .changeset/verdict-memo-flight-no-reask.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,4 +2,4 @@
2
2
"@solidjs/signals": patch
3
3
---
4
4
5
-
An async memo that reads a memo using `latest()` or `isPending()` no longer asks the same question again when that memo re-asks. Reading such a memo makes the reader a verdict reader too (F-6), and a verdict reader is re-derived when its source goes pending. The re-derive was served the committed value that the memo had already derived from, so it repeated the request. That extra flight then held the verdict lane, and the landing ran it a third time on the same input. Now an async reader that opened no `isPending()` or `latest()` window of its own goes pending with the flight, like any other derivation, and asks once when the flight lands. Sync readers re-derive as before.
5
+
An async memo that reads a memo using `latest()` or `isPending()` no longer asks the same question twice. Reading such a memo made the async memo a verdict reader too (F-6). So it was re-derived each time one of its verdict sources went pending, and it was served committed values that a hold had already moved past. Each time, it asked a question it had already answered. With two verdict sources, it could ask a stale question after both had landed. An async memo that opens no `isPending()` or `latest()` window of its own now takes no verdict role. It waits on its sources like any other derivation and asks each question once. Sync memos are unchanged.
Copy file name to clipboardExpand all lines: packages/signals/docs/RULES-INDEX.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ Status legend: **live** stated and standing · **ruled** carries an explicit rul
54
54
| A7 | amended |`docs/SPEC-ASYNC-SEMANTICS.md:165`| — | fuzz-findings-l2.test.ts×1 spec-async-semantics.test.ts×2 visibility-oracle-store.states.ts×1 visibility-oracle.states.ts×1 visibility-oracle.test.ts×1 |[ruled, amended in place] Resolved async never reads `[false, undefined]` — After an async memo resolves, `[isPending(x), latest(x)]` is `[false, resolvedValue]` — never `[false, undefined]`. **Amende… |
55
55
| A8 | amended |`docs/SPEC-ASYNC-SEMANTICS.md:173`| — | create-deferred-3710.test.ts×1 createMemo.test.ts×1 visibility-oracle-store.states.ts×1 visibility-oracle.states.ts×2 |[ruled, amended in place 2026-07-07]`isPending(() => latest(x))` follows `x`'s own async only — verdicts are per-channel — (**re-ruled 2026-07-07c** — was "tracks the transition the same as `isPendin… |
56
56
| A9 | amended |`docs/SPEC-ASYNC-SEMANTICS.md:181`| projection.ts×1 target.ts×1 | spec-async-semantics.test.ts×3 visibility-oracle-store.states.ts×4 visibility-oracle-store.test.ts×1 |[ruled, amended in place 2026-07-07] Store leaves behind a firewall report the firewall's new-question refetch — `isPending` on a store leaf behind a firewall reports the firewall's refetch like any a… |
57
-
| A10 | ruled |`docs/SPEC-ASYNC-SEMANTICS.md:189`|async.ts×1 core.ts×3 verdict.ts×2 | createMemo.test.ts×1 fuzz-findings-l2.test.ts×1 ispending-memo-unstamped-hold-3457.test.ts×2 latest-isPending-consistency.test.ts×3 verdict-contract.test.ts×2 verdict-memo-flight-no-reask.test.ts×1 |[ruled]`[isPending(x), x()]` is atomic within one scope — `[isPending(x), x()]` read in one scope is atomic: a reader that observed the fresh value must not see `pending === true` for it. |
57
+
| A10 | ruled |`docs/SPEC-ASYNC-SEMANTICS.md:189`| core.ts×4 verdict.ts×2 | createMemo.test.ts×1 fuzz-findings-l2.test.ts×1 ispending-memo-unstamped-hold-3457.test.ts×2 latest-isPending-consistency.test.ts×3 verdict-contract.test.ts×2 verdict-memo-flight-no-reask.test.ts×1 |[ruled]`[isPending(x), x()]` is atomic within one scope — `[isPending(x), x()]` read in one scope is atomic: a reader that observed the fresh value must not see `pending === true` for it. |
58
58
| A11 | ruled |`docs/SPEC-ASYNC-SEMANTICS.md:103`| — | latest-isPending-consistency.test.ts×1 loading-fallback-in-flush-3540.test.ts×2 visibility-oracle-store.states.ts×2 visibility-oracle.states.ts×1 |[ruled] Sync derivations of held sources are visible through `latest()`/`isPending()` — Sync derivations of transition-held sources are visible through `latest()`/`isPending()` (held sync recompute is… |
59
59
| A12 | amended |`docs/SPEC-ASYNC-SEMANTICS.md:197`| — | createOptimistic.test.ts×2 spec-async-semantics.test.ts×1 |[ruled, amended in place] Resting optimistic nodes report pending like a plain memo — A resting optimistic node reports pending via exactly the causes a plain async memo does (A19) — a reverting optim… |
60
60
| A13 | ruled |`docs/SPEC-ASYNC-SEMANTICS.md:205`| — | spec-async-semantics.test.ts×7 |[ruled 2026-07-06 (promoted from B1)] Resting optimistic ≡ plain async memo at every checkpoint — (was B1) A resting optimistic node (no active override) is observationally identical to a plain async … |
0 commit comments