oracle-gaps: a mutant's outcome can depend on its batch (setup-error in a full run, killed with --only)
Les mainteneurs répondent en général sous 1 jour
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Accessibilité débutants
- 18/100
- Type d'issue
- Bug
- Clarté
- Plutôt claire
- Activité
- Active
- Stack technique
- javascript, node.js
- Domaine
- testing
Piste de recherche
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.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
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.
- Langage dominant
- JavaScript
- Étoiles
- 5
- Forks
- 1
- Merge moyen
- 8 h 31 min
- PR mergées (30 j)
- 60
Préparer son environnement
Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de TanStack/oracles
-
Difficulté 2/5 1-3 heures Accessibilité débutants 62/100
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 64/100
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 25/100
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 35/100
Les mainteneurs répondent en général sous 1 jour
Toutes les issues de TanStack/oracles
Issues similaires
-
Difficulté 2/5 1-3 heures Accessibilité débutants 82/100
-
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
Les mainteneurs répondent en général sous 1 jour
-
Edit: Telemante [YT]Ouvertechannels:edit check:passed
Difficulté 2/5 1-3 heures Accessibilité débutants 65/100
Les mainteneurs répondent en général sous 1 jour
-
bug
Difficulté 2/5 1-3 heures Accessibilité débutants 84/100
swc-project/swc-next-issues#490 ·
-
[workshop-sim] Improve: Add predict-and-check practice and checkpoint to Step 4 Actions introOuvertefeedback simulation workshop
Difficulté 2/5 1-3 heures Accessibilité débutants 69/100
githubnext/gh-aw-workshop#5826 ·
Les mainteneurs répondent en général sous 1 jour