oracle-gaps: a mutant's outcome can depend on its batch (setup-error in a full run, killed with --only)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 18/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- javascript, node.js
- Área
- testing
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- JavaScript
- Estrellas
- 5
- Forks
- 1
- Merge medio
- 8 h 31 min
- PR fusionados (30 d)
- 60
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de TanStack/oracles
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
Los mantenedores suelen responder en 1 día
Todos los issues de TanStack/oracles
Issues similares
-
Edit: Telemante [YT]Abiertochannels:edit check:passed
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
Los mantenedores suelen responder en 1 día
-
fix
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
idean3885/claude-ops-agent#1083 ·
Los mantenedores suelen responder en 1 día
-
入群码过期Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 84/100
aliyun/ai-agent-handbook#29 · 1 comentario ·
-
docs documentation need-triage SaaS
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
apache/cloudstack#14719 ·
Los mantenedores suelen responder en 1 día