oracle-gaps: a mutant's outcome can depend on its batch (setup-error in a full run, killed with --only)
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 18/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- javascript, node.js
- Ambito
- testing
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- JavaScript
- Stelle
- 5
- Fork
- 1
- Merge medio
- 6h
- PR unite (30g)
- 56
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di TanStack/oracles
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 64/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
TanStack/oracles#120 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
windows
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
TanStack/oracles#118 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di TanStack/oracles
Issue simili
-
Edit: Telemante [YT]Apertachannels:edit check:passed
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
I maintainer di solito rispondono entro 1 giorno
-
fix
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
idean3885/claude-ops-agent#1083 ·
I maintainer di solito rispondono entro 1 giorno
-
入群码过期Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 84/100
aliyun/ai-agent-handbook#29 · 1 commento ·
-
docs documentation need-triage SaaS
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
apache/cloudstack#14719 ·
I maintainer di solito rispondono entro 1 giorno