[2.0 next, regressed after rc.13] Async-generator action times out on its authoritative live echo
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- backend
Research direction
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.
Written by the indexing model from the issue text.
Description
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
Steps to Reproduce the Bug or Issue
- 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.
}
- 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/webnext at3086f1b77cd7b0431d3a7f768c2984c335758633; comparison2.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.
- Dominant language
- TypeScript
- Stars
- 36.1k
- Forks
- 1.1k
- Avg merge
- 11h 42m
- Merged PRs (30d)
- 326
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from solidjs/solid
-
Difficulty 3/5 Half a day Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
Similar issues
-
bug priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Automattic/data-liberation-agent#685 ·
Maintainers usually reply within 1 day
-
Business
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
txn2/mcp-data-platform#2063 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 77/100
Crosstalk-Solutions/project-nomad#1427 ·
Maintainers usually reply within 2 days