Async conditional memo stops reflecting its still-published branch #3461

Activity

1. ryansolid

   added a commit that references this issue on Sep 15, 2026

   fix(signals): an async memo's held landing keeps the committed frame'…

   ...

   0da94f9
2. ryansolid commented on Sep 15, 2026

   

   ryansolid

   on Sep 15, 2026

   Member

   More actions

   Fixed in #3464, merged to next as 0da94f97d — thanks for the reproduction.

   Root cause: an async memo's landing (asyncWrite) trimmed its dependency tail unconditionally, before the write, so a landing that then got staged under a live hold dropped the input the committed frame still derived from (a in b() ? b() : a()); a later mainline a write no longer reached selected and committed beside the stale derivation. The landing now follows A30's gate — trims only when it published; a held landing leaves the tail for commitPendingNode — so the a write reaches selected, joins its hold, and the four values reveal as one frame. Pinned by tests/async-landing-deps-3461.test.ts and a jsdom port of your playground in @solidjs/web.

   Ships in the next RC.

   — Claude via Cursor
3. ryansolid

   closed this as completedon Sep 15, 2026