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

[2.0 next, regressed after rc.13] Async-generator action times out on its authoritative live echo

Cerrado
  • ¿Algo no está bien?
#3,898 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
backend

Línea de trabajo

Compare the current SolidJS HEAD with the 2.0.0-rc.13 tag to identify the regression in async-generator action handling. Focus on the action and until implementations to understand why the live acknowledgement is missed when the source already contains the expected value. Use the provided reproduction to verify any fix.

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

Descripción

Describe the bug

An async-generator action can time out waiting for a live acknowledgement even after the real source contains that acknowledgement.

Your Example Website or App

Standalone reproduction

Steps to Reproduce the Bug or Issue
  1. Use the source below with the selected Solid build (complete setup is linked above).
import { action, createOptimisticStore, createSignal, flush, until } from "solid-js";
export default function App() {
  const [source, setSource] = createSignal<{ clientId: string }[]>([]);
  const [rows, setRows] = createOptimisticStore(() => source(), []);
  const [result, setResult] = createSignal("idle");
  const save = action(async function* () {
    setRows((draft) => {
      draft.push({ clientId: "c1" });
    });
    await 0; // Fire-and-forget send resumes outside the action context.
    yield until(() => rows.some((row) => row.clientId === "c1"), { timeout: 100 });
  });
  function run() {
    setResult("waiting");
    save().then(
      () => setResult("confirmed"),
      (error) => setResult(String(error)),
    );
    setTimeout(() => {
      setSource([{ clientId: "c1" }]);
      flush();
    }, 20);
  }
  return (
    <>
      <button id="trigger" onClick={run}>
        Send and acknowledge
      </button>
      <output id="answer">{result()}</output>
    </>
  ); // The real source acknowledges c1, but HEAD times out.
}
  1. Paste into a Solid 2 playground. Click Send and acknowledge, then wait 100 ms.
Expected behavior

Expected: The output becomes confirmed after the source receives c1.
Actual: HEAD displays TimeoutError.

Platform
  • Solid: solid-js / @solidjs/web next at 3086f1b77cd7b0431d3a7f768c2984c335758633; comparison 2.0.0-rc.13. Signals, compiler and diagnostics match the selected Solid build.
  • OS: macOS 26.6.2 (25G83); browser cases: system Google Chrome 155.0.8059.40. Server-only/type checks run in Bun 1.4.2.
  • Builds/comparison: development and production fail. rc.13 passes in both builds.
Additional context

The real source contains the acknowledged row, yet the action continues waiting until its timeout. Adding a yield after await avoids the failure.

Adding a bare yield after await 0 avoids the timeout. rc.13 needs no such change; the intended context requirement remains an upstream decision.

Related: #3687

Full automated reproduction

One-command setup, run and expected output.

Copy the standalone files into a fresh Bun project. The displayed snippet is executed by snippet.test.ts. The original automated case is also retained.

bun init -y
bun add [email protected] @solidjs/[email protected] @solidjs/[email protected] @solidjs/[email protected] @solidjs/[email protected]
bun add -d playwright
bun run link-head.ts /absolute/path/to/built/solid
BUILD_MODE=development bun test ./snippet.test.ts

The five linked packages must come from the same built HEAD checkout. Omitting the link step selects the rc.13 comparison. Chrome runs use the system installation.

Lenguaje dominante
TypeScript
Estrellas
36.1k
Forks
1.1k
Merge medio
11 h 37 min
PR fusionados (30 d)
344

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.