Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

2.0.0-rc.13 async isPending derivation makes rendered memo values disagree

Closed
  • Is something wrong?
#3,766 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, typescript
Domain
frontend, performance

Research direction

Start with the linked reproduction and inspect the compiled JSX and connected DOM behavior described there, comparing the two reads of gate() during the delayed update. The payload names no source file or test; done means both visible gate() values remain consistent while the pending state is held or revealed, including against the current next runtime.

Written by the indexing model from the issue text.

Description

Describe the bug

Two JSX expressions read the same async memo, gate(). After an update, one displays 200 while the other still displays 100 for about three seconds.

The second expression also reads an async derivation of isPending(source). Retaining its previous pending value while the correction waits is understandable, but this also leaves its ordinary gate() read disagreeing with the other visible expression.

Your Example Website or App

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

Steps to Reproduce the Bug or Issue
  1. Wait for initialization (about three seconds), until both rows show false | 100.
  2. Click Run.
  3. After about 300ms, the first row shows true | 200 and the second shows true | 100.
  4. The different right-hand values remain visible for about three seconds. Both rows eventually show false | 200.
Expected behavior

The two visible reads of the ordinary memo gate() should agree while this update is held or revealed. This does not require the pending boolean to immediately become false: the delayed pending correction can remain held without showing two different values of gate() at once.

Screenshots or Videos

No response

Platform
  • OS: Linux
  • Browser: Chromium 151.0.7922.173
  • Solid: 2.0.0-rc.13; also reproduced with current next at e44b2e4.
Additional context

Verified with compiled JSX and connected DOM in both development and production, including builds of the current next runtime and JSX compiler. There are no imperative reads, latest() calls, or loading boundaries in this example.

Two controls remove the mismatch:

  • Change the pending-true delay from 300 to 50, so the child resolves before its parents: both rows show true | 200 during the hold.
  • Make slow synchronous by returning value instead of delay(...): both rows show false | 200 after the parent work resolves.
Dominant language
TypeScript
Stars
36.1k
Forks
1.1k
Avg merge
13h 13m
Merged PRs (30d)
306

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from solidjs/solid

All issues in solidjs/solid

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.