Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

New async memo reveals a held signal update early

Abierto
  • ¿Algo no está bien?
#3,800 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript, typescript
Área
frontend

Línea de trabajo

Start by reading the async memo and scheduled render-effect behavior in the repository, then compare the issue’s reproduction with the earlier report #3408. The linked playground reproduces the early reveal; no source file or test is named, so locate or add focused coverage for synchronous versus asynchronous first results and the explicit flush. Done when the new observer remains held until the slow derivation settles.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Describe the bug

A newly created async memo reads an update that is still held by an existing async derivation, then notifies a scheduled render effect before that update is revealed. The existing scheduled render effect still last reported count = 1, slow = 1, while the new one reports 2.

The same newly created memo stays held when its first result is synchronous. Returning Promise.resolve(count()) instead makes it reveal early.

Your Example Website or App

https://s.olid.uk/id/22KYZfNOSnqqlHlUzL1MqQ

Steps to Reproduce the Bug or Issue
  1. Open the playground console and press Build (or reload).
  2. After about one second, observe parent 1 1.
  3. About 100ms later, observe child 2 while the parent is still held at 1 1.
  4. Roughly one second after that, the slow derivation settles and the parent finally reports parent 2 2.
Expected behavior

The new scheduled render observer should stay held until the input update can be revealed with its slow derivation. An asynchronous first result should preserve the inherited hold, just as a synchronous first result does.

Screenshots or Videos

No response

Platform
  • OS: Linux
  • Browser: Chromium 151.0.7922.173
  • Solid: 2.0.0-rc.13 in the playground; also reproduced on upstream next at b0bad02, in development and production.
Additional context

Both render effects use { schedule: true }, so this excludes the immediate mounting-effect path. The repro uses only primitives.

Two controls preserve the hold:

  • Replace Promise.resolve(count()) with count().
  • Remove the explicit flush() before creating the new memo.

The development warnings about unowned effects are expected in this minimal repro.

Related earlier report: #3408. Here the synchronous first result behaves correctly; the asynchronous first result does not.

Lenguaje dominante
TypeScript
Estrellas
36.1k
Forks
1.1k
Merge medio
10 h 7 min
PR fusionados (30 d)
289

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de solidjs/solid

Todos los issues de solidjs/solid

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.