oracle-gaps: a mutant's outcome can depend on its batch (setup-error in a full run, killed with --only)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 18/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- javascript, node.js
- 领域
- testing
调研方向
Start with capture-setup.mjs, which resets the module registry and deletes new globals between copies but does not restore existing builtin prototypes. The report IDs in the issue (2026-11-12T23-35-42-301Z-3e2c4991 and the --only replay 2026-11-12T23-37-41-738Z-d866fd67) show the same mutants changing outcome with batch composition. Done means a deterministic witness in which one mutant's outcome depends on an earlier mutant in the same worker, and a fix that makes --only and full runs agree. Expect to ask the maintainers how to pin batch order first.
由索引模型根据 Issue 内容生成。
描述
Summary
In one onboarding run (klona, r20), two mutants were reported as setup-error in a full gap check, but a replay with --only killed both of them. A mutant's outcome must not depend on what else is in its batch: --only must give the result that the full run gives.
Evidence (unverified, from the r20 session)
- Repository:
/tmp/oracle-validation/r20/codex-klona/repo. The notes are inoracles-feedback.md, beside the run log. - Full run report
2026-11-12T23-35-42-301Z-3e2c4991: JSON mutants M21 and M22 weresetup-error, withSpread syntax requires ...iterable[Symbol.iterator] to be a function. Production was unchanged and every baseline test passed. - An isolated replay right afterwards,
--only json.js:M21,json.js:M22(report2026-11-12T23-37-41-738Z-d866fd67), killed both under the lawarray slots. - A full replay with the fork pool reproduced the setup errors (report
2026-11-12T23-38-22-238Z-fd6a91f0), so worker isolation did not change the result. - In two later complete runs, the discrepancy did not recur.
Hypothesis (not confirmed)
The cause is global state carried from one copy to the next. Each copy resets its module registry and deletes the global names that the worker did not have at first (capture-setup.mjs). It does not undo changes to existing builtins, such as a property written on Array.prototype or Object.prototype. Klona's pollution-safety laws show that its mutants can write there. A polluting mutant that runs earlier in the same worker would then break a later copy's module load or setup (...iterable[Symbol.iterator]), which is reported as a setup-error that --only does not reproduce.
This is a different mechanism from the copy-path seed defect fixed in the follow-up PR for #48 (each copy seeded Math.random by its copy path). That defect affected every copy, so --only would show it too.
What a fix needs
- A witness in which a mutant's outcome changes with batch composition. It needs two mutants in one worker, in a known order, with the first writing to a builtin prototype. The runner's scheduling does not fix that order today, so a deterministic witness may need a way to pin a batch.
- Then, possibly: snapshot and restore builtin prototypes between copies, or run each copy that writes to them in a fresh worker.
- 主要语言
- JavaScript
- 星标
- 5
- 派生
- 1
- 平均合并
- 8 小时 31 分钟
- 30 天内合并 PR
- 60
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
TanStack/oracles 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 64/100
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 35/100
维护者通常 1 天内回复
相似的 Issue
-
channels:edit check:passed
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
fix
难度 2/5 1-3 小时 新手友好度 68/100
idean3885/claude-ops-agent#1083 ·
维护者通常 1 天内回复
-
入群码过期未关闭
难度 1/5 1 小时以内 新手友好度 84/100
aliyun/ai-agent-handbook#29 · 1 条评论 ·
-
docs documentation need-triage SaaS
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 76/100
apache/cloudstack#14719 ·
维护者通常 1 天内回复