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
[2.0 / next] An unowned memo with an isPending() reader skips its recompute: reads undefined after a landing, or keeps a stale value after an error recovers #4366
Found by the async app generator (packages/web/test/async-gen, branch claude/project-thread-bgafe5), minimized. Both shapes need module-level (unowned) memos and an isPending(m1) reader. Created inside the component, or without the isPending read, both are correct.
Shape 1: reads undefined after the first landing
letrelease;constm0=createMemo(()=>newPromise(r=>(release=r)));constm1=createMemo(()=>m0()+1);render(()=>(<Loadingfallback="[L]"><Showwhen={m0()}><span>{String(isPending(m1))}{String(m1())}</span></Show></Loading>),el);flush();release(2);// after settling: <span>false NaN</span>, expected <span>false 3</span>
Shape 2: a stale value after the source recovers from an error
Activity
fix(signals): an isPending probe wakes a dormant memo outside its win…
ryansolid commentedon Oct 28, 2026
Fixed on
nextby #4381 (4d8195d); it ships in the next RC.Generated by Claude Code