oracle-gaps: a mutant's outcome can depend on its batch (setup-error in a full run, killed with --only)
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 18/100
- Issue-Typ
- Bug
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- javascript, node.js
- Bereich
- testing
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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.
- Vorherrschende Sprache
- JavaScript
- Sterne
- 5
- Forks
- 1
- Ø Merge
- 6 Std.
- Gemergte PRs (30 T.)
- 56
Entwicklungsumgebung
Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus TanStack/oracles
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 62/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 64/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 48/100
TanStack/oracles#120 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
windows
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 48/100
TanStack/oracles#118 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in TanStack/oracles
Ähnliche Issues
-
Edit: Telemante [YT]Offenchannels:edit check:passed
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
Maintainer antworten meist innerhalb von 1 Tag
-
fix
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
idean3885/claude-ops-agent#1083 ·
Maintainer antworten meist innerhalb von 1 Tag
-
入群码过期Offen
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 84/100
aliyun/ai-agent-handbook#29 · 1 Kommentar ·
-
docs documentation need-triage SaaS
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
apache/cloudstack#14719 ·
Maintainer antworten meist innerhalb von 1 Tag