2.0.0-rc.20: a memo that calls isPending()/latest() on an unrelated signal makes a branch opened by a held update read the pre-hold world; <Loading> never settles
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 8/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
- 领域
- frontend
调研方向
The reproduction is the it.each block around arrive(probe), which renders a Loading root with a Show branch and runs the three probes against the chrome memo. Start by reading how isPending and latest interact with memo reads inside a held Loading boundary, then run the three probes to confirm plain read passes and the other two hang on root. Done means all three probes return rows and the held update settles, which requires understanding the signals reactivity internals, not a local edit.
由索引模型根据 Issue 内容生成。
描述
Describe the bug
A held update (an async memo under the root <Loading>) writes session and opens <Show when={session() !== undefined}>. Inside, params is a memo that reads session and a chrome memo; chrome reads an unrelated signal plan, which is written afterwards outside the hold.
If chrome reads plan plainly, the branch reads session as "acc" and the hold lands. If chrome calls isPending(plan) or latest(plan) instead, params observes signedIn: false inside the branch whose condition already observed session !== undefined. The branch reads a lazy memo that never resolves (only reachable while signed out), and the root <Loading> stays on root forever.
Two plain reads of session on one screen disagree (the tear RULES-DERIVED.md D-27 forbids), and a display-ahead reader ends up holding the change it read ahead of (contradicts F-6: "display-ahead readers never hold the change they read ahead of").
Reproduces on rc.13, rc.20 and next@215c365 (not a regression). Related closed issues: #4010, #4426.
Steps to Reproduce
import { render } from "@solidjs/web";
import { createMemo, createSignal, isPending, Loading, latest, Show } from "solid-js";
import { expect, it } from "vitest";
const wait = (ms: number) => new Promise((r) => setTimeout(r, ms));
const NEVER = new Promise<never>(() => {});
type Probe = "plain read" | "isPending" | "latest";
async function arrive(probe: Probe): Promise<string | null | undefined> {
const [session, setSession] = createSignal<string | undefined>(undefined);
const [plan, setPlan] = createSignal(false);
const [gate, setGate] = createSignal(0);
let release: () => void = () => {};
function Page() {
// The only difference between the cases is how this memo reads `plan`.
const chrome = createMemo(() =>
probe === "isPending" ? (isPending(plan), plan()) : probe === "latest" ? latest(plan) : plan(),
);
const params = createMemo(() => ({ plan: chrome(), signedIn: session() !== undefined }));
const signedOutOnly = createMemo(() => NEVER, { lazy: true });
return (
<Show when={session() !== undefined} fallback={<i>signed out</i>}>
<b>{params().signedIn ? "rows" : signedOutOnly()}</b>
</Show>
);
}
const held = createMemo(() => {
const g = gate();
return g === 0 ? g : new Promise<number>((r) => (release = () => r(g)));
});
const el = document.createElement("div");
const dispose = render(
() => (
<Loading fallback={<i>root</i>}>
<span>{held()}</span>
<Page />
</Loading>
),
el,
);
await wait(10);
setGate(1);
setSession("acc");
await wait(5);
setPlan(true);
await wait(5);
release();
await wait(50);
const out = el.querySelector("b")?.textContent ?? el.querySelector("i")?.textContent;
dispose();
return out;
}
it.each<Probe>(["plain read", "isPending", "latest"])(
"%s of an unrelated signal upstream: the branch the hold opens reads the hold's session and the hold lands",
async (probe) => {
expect(await arrive(probe)).toBe("rows");
},
);
package.json
{
"name": "solid-repro",
"private": true,
"type": "module",
"scripts": { "test": "vitest run" },
"dependencies": {
"solid-js": "2.0.0-rc.20",
"@solidjs/web": "2.0.0-rc.20",
"@solidjs/signals": "2.0.0-rc.20"
},
"devDependencies": {
"@solidjs/vite-plugin": "3.0.0-next.54",
"jsdom": "30.1.2",
"vitest": "5.0.5"
}
}
vitest.config.ts
import solid from "@solidjs/vite-plugin";
import { defineConfig } from "vitest/config";
export default defineConfig({
plugins: [solid()],
test: { environment: "jsdom" },
});
Expected behavior
rows for all three probes: the only difference is how chrome reads an unrelated signal.
Actual behavior
plain read → rows; isPending and latest → root forever.
- 主要语言
- TypeScript
- 星标
- 36.2k
- 派生
- 1.1k
- 平均合并
- 11 小时 5 分钟
- 30 天内合并 PR
- 475
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
solidjs/solid 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 28/100
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 12/100
维护者通常 1 天内回复
-
[2.0 / next] <Errored> recovery shows a pending memo's answer to an older input beside the new input未关闭
难度 4/5 3-5 天 新手友好度 20/100
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 15/100
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 18/100
维护者通常 1 天内回复
相似的 Issue
-
needs-triage
难度 2/5 1-3 小时 新手友好度 66/100
microsoft/playwright#43875 · 1 条评论 ·
维护者通常 1 天内回复
-
feature
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1 小时以内 新手友好度 88/100
adobe/react-spectrum#10909 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
-
Run the dependency drift check可能已有人在做 @spaceninja 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 72/100
cloudfour/lighthouse-parade#449 ·
维护者通常 1 天内回复