gap CLI: a run under load can end non-zero (an internal error) where it should complete
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
- 30/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- javascript, nodejs
Línea de trabajo
Start from packages/oracles and run the failing shard command with the replay env vars (ORACLE_SEED=20261105 ORACLE_PATH=1 ORACLE_PROPERTY=oracle-gaps.report) while a CPU hog saturates the machine, as the issue's Next section proposes. Read oracle-gaps/vitest.config.mjs and scripts/pr-shards.mjs to understand shard selection, and note that #55 now prints the error log on exit 3. Done means the shard-3 e2e run completes exit 0 under load, with the brokenOwner history blocked rather than refused.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
Under load, the gap CLI sometimes ends a run with a non-zero exit where the run should complete. Twice it was an internal error ("This is a bug in oracle-gaps"). The e2e oracle's fixed-seed shard 3 failed in 2 of 8 Linux runs on #55's head. Each failure had a different symptom, and neither one reproduces when the unit runs alone.
Traces
- CI, job 132489470739 (run 43608937018), commit 16f510c, "Gap report end-to-end oracle (fixed seed, 3/3)":
- Unit:
fixed seed 20261105: generated, historyORACLE_PATH=1(faultbrokenOwner). - Error:
a history entered "refused brokenOwner", which the property does not declare. - Meaning: the CLI exited non-zero on a
brokenOwnerhistory. The history owes exit 0 with blocked mutants (blocked by brokenOwner). The log does not show which non-zero exit or its error.log. - Replay:
ORACLE_SEED=20261105 ORACLE_PATH=1 ORACLE_PROPERTY='oracle-gaps.report' ORACLE_UNIT='random seed: generated' vitest run -t '^oracle-gaps\.report(?: | > )random seed: generated$'
- Unit:
- Classic Arca VM, tag r55-gen-shard3, commit edb24ba (16f510c plus a test-only diagnostic), the same shard-3 command:
- Unit:
fixed seed 20261105: an edit sequence through the daemon, stepdieMidCheck. - Error:
through the daemon at dieMidCheck: the run wrote a line on stderr that is not a line of the stream: This is a bug in oracle-gaps, not in your oracle. Its stack is in <package>/out-daemon/error.log. - The VM was shared with another session's long loops when this ran.
- Unit:
The shard command, from packages/oracles:
pnpm exec vitest --run --maxWorkers=2 --config oracle-gaps/vitest.config.mjs gap-report-oracle -t "$(node scripts/pr-shards.mjs pattern oracle-gaps-fixed-seed 3)"
Tally
| Commit | Where | Shard-3 runs | Failed |
|---|---|---|---|
| 16f510c (#55 head) | CI, Classic Arca, Arclets | 8 | 2 |
35422e3 (main) |
Classic Arca, Arclets | 6 | 0 |
| ed091f3 (#55 before the #58 merge) | Arclets | 4 | 0 |
The unit generated alone passed on 16f510c locally (macOS) and on the VM, and on main locally. All 12 runs on the dedicated Arclets passed, with no internal error.
Next
- Reproduce under load on purpose: shard 3 with a CPU hog on the Arclets, 4 runs on #55's head (with the diagnostics, which print each exit-3 run's error.log) and 4 on
main. The result decides whether this is #55's or older. - #55 (b959d4c) now makes the incremental violation print a cold run's error log when that run exits 3, so the next failure in CI shows its stack.
- Related: the deterministic-cut follow-up (cut runs by work count, not wall time; "determinism under load"), which targets timing-dependent outcomes.
This issue was written by Isaac.
- 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
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
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
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
swc-project/swc-next-issues#490 ·
-
[workshop-sim] Improve: Add predict-and-check practice and checkpoint to Step 4 Actions introAbiertofeedback simulation workshop
Dificultad 2/5 1-3 horas Aptitud para principiantes 69/100
githubnext/gh-aw-workshop#5826 ·
Los mantenedores suelen responder en 1 día