2.0.0-rc.13 async isPending derivation makes rendered memo values disagree
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- javascript, typescript
- 领域
- frontend, performance
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
- Wait for initialization (about three seconds), until both rows show
false | 100. - Click Run.
- After about 300ms, the first row shows
true | 200and the second showstrue | 100. - 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
nextat 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
300to50, so the child resolves before its parents: both rows showtrue | 200during the hold. - Make
slowsynchronous by returningvalueinstead ofdelay(...): both rows showfalse | 200after the parent work resolves.
- 主要语言
- TypeScript
- 星标
- 36.1k
- 派生
- 1.1k
- 平均合并
- 11 小时 42 分钟
- 30 天内合并 PR
- 326
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
solidjs/solid 的其他 Issue
-
[2.0 next, regressed after rc.13] Async-generator action times out on its authoritative live echo未关闭
难度 3/5 1-2 天 新手友好度 55/100
维护者通常 1 天内回复
-
难度 3/5 半天 新手友好度 75/100
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 64/100
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 55/100
维护者通常 1 天内回复
相似的 Issue
-
[bug] diagnostics.dumpBody：Buffer 形态请求（透传 lane）跳过 dumps/ 落盘，仅留 raw/-unknown-可能已有人在做 @ranxianglei 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 62/100
ranxianglei/billion-context#2421 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
platformatic/mcp#216 ·
维护者通常 1 天内回复
-
pending triage
难度 2/5 1-3 小时 新手友好度 76/100
nuxt/test-utils#1842 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
MoonshotAI/kimi-code#4146 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
farbenmeer/tapi#531 ·