Ordered loader retains earlier requests after a newer authoritative read succeeds
维护者通常 1 天内回复
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
调研方向
Start with packages/db/tests/query/ordered-source-loader-state-oracle.test.ts, especially checkAuthorityCase near line 1632, and replay the recorded seed and path on the specified commit. Compare production request retirement with the oracle’s model and observation checkpoint, then exercise the nearby synchronous repair, release-triggered truncate, and joined-work histories. Done means the original failure is reproduced, a repair passes the shared comparisons, a hostile mutant fails, and a real Collection or provider witness supports any public resource claim.
由索引模型根据 Issue 内容生成。
描述
The Release workflow for the first RC failed the ordered-loader request-authority oracle on merged release commit 71bf598a3d13d37db28ac112431fd8be790957fe (#2217).
Executed CI evidence
- Failed Test (db-2) job
- Owner:
packages/db/tests/query/ordered-source-loader-state-oracle.test.ts - Test:
holds, retires, and recovers requests under generated settlement orders (random campaign) - Property:
ordered-loader.request-authority - Seed:
-845274422 - Path:
2109:1:3:6:4:8:10:13:15 - Failed after 2,110 generated tests, shrunk eight times.
- Assertion checkpoint:
checkAuthorityCase, line 1632, after the history drain and any explicit retry.
no leak: requests [3,4] are still held after authoritative request 5 succeeded
{"indexed":false,"limit":1,"settledFirst":true,"releaseFault":false,"syncRepair":true,"requiresFullSource":false,"joined":true,"snapshotRows":1,"needsMore":true,"retryTimer":false,"releaseTruncates":true,"offset":0,"releaseReenters":false,"releaseDisposes":false,"history":[{"type":"settle","pick":0,"ok":true},{"type":"settle","pick":0,"ok":true},{"type":"report","react":false},{"type":"move","delta":-1},{"type":"joinedBusy"},{"type":"settleNewest"}]}
Accepted law and limits of this report
The owner's “No leak” law states that once loading is quiet and no failure blocks it, the loader holds nothing issued before its last successful authoritative read. Retained demands can be read again on later refetches. The oracle uses the real loader with a controlled subscription; this mismatch establishes a failing request-ledger comparison, not incorrect public query rows or a measured production resource leak. Diagnose production retirement versus the oracle's model, replay ownership and observation checkpoint before changing either one.
This exact trace has not yet been replayed independently. The observed assertion is from the executed CI run; it is not a timeout or a reach failure.
Replay
Run from packages/db on the recorded commit:
TANSTACK_DB_ORACLE_PROPERTY=ordered-loader.request-authority \
TANSTACK_DB_ORACLE_SEED=-845274422 \
TANSTACK_DB_ORACLE_PATH=2109:1:3:6:4:8:10:13:15 \
pnpm exec vitest run --coverage.enabled=false --typecheck.enabled=false \
tests/query/ordered-source-loader-state-oracle.test.ts -t 'random campaign'
Keep this history in the shared comparison and exercise nearby synchronous repair, release-triggered truncate and joined-work histories before a production repair. Show RED on the original code, GREEN after repair and a hostile mutant that fails. A real Collection/provider receiving witness is needed before claiming the public resource consequence is closed.
Related loader retirement investigations: #2223 (failed request across cursor reset) and #2191 (request authority/retirement). This trace has only successful explicit settlements; identity with either earlier report is not established. It is separate from the publication-retention report #2294 and multi-tab Electric report #2281.
The maintainer explicitly approved recording this counterexample as a follow-up and retrying the first RC release while leaving the defect open. No test, comparison or run budget has been weakened. A passing retry does not close this issue.
- 主要语言
- TypeScript
- 星标
- 4k
- 派生
- 277
- 平均合并
- 1 天 6 小时
- 30 天内合并 PR
- 199
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
TanStack/db 的其他 Issue
-
难度 1/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
OfflineExecutor.dispose() never settles pendingTransactionPromises可能已有人在做 @Claire-ovo 于 4 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
Two @tanstack/db tests time out under CPU load because a cold module import counts against the 5 s default timeout可能已有人在做 @jp-knj 于 2 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
维护者通常 1 天内回复
相似的 Issue
-
Replace discontinued crypto-js in the theme可能已有人在做 @aelmanaa 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 85/100
PaloAltoNetworks/docusaurus-openapi-docs#1689 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
solana-foundation/solana-web3.js#4015 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
-
documentation
难度 1/5 1-3 小时 新手友好度 90/100
ivopogace/opencode-courier#422 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
chapel-lang/chapel-vscode#158 ·
维护者通常 1 天内回复