constructed-order.json is a stale prefix: 19 constructed histories are unrecorded

Abierto
#183 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
javascript, node.js
Área
testing

Línea de trabajo

Read packages/oracles/oracle-gaps/constructed-order.json and the canary in packages/oracles/tests/gap-report-history-fingerprint.test.ts. Compare the recorded 90 names with the 109 current constructed histories using the fixed seed 20261105, then update the list and canary to catch missing entries. Done means the recorded order includes all histories and the test fails if a history is omitted or inserted before a recorded one.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

packages/oracles/oracle-gaps/constructed-order.json is a stale prefix of the constructed histories of the gap e2e oracle. The canary appends new constructed histories, and never inserts one before a recorded one (packages/oracles/tests/gap-report-history-fingerprint.test.ts) only checks that the recorded list is a prefix of the current list, so the 19 missing names are not caught.

Measured at 11d5aa3d (plus the #182 fix on top, which adds the last one):

  • current constructed histories (fixed seed 20261105 units): 109
  • recorded in constructed-order.json: 90 (a valid prefix)
  • missing: 19

Missing names, in current order:

  • a slow owner's kill and another owner's kill
  • a backstop cut ends the copies ahead of a later kill
  • a kill past the work budget in a later owner
  • a slow kill after a 16 s wait
  • a copy waiting on a timer
  • a copy waiting on an unref'd timer
  • a copy waiting on a pipe it opened
  • a copy beside the runner's pending write
  • a copy beside the runner's pending timer
  • a clocked copy that spins
  • an authored mutant whose owner hangs
  • a stream log lost after its note, then stopped, unsupervised
  • a heavy test that reads the clock after its work
  • a heavy test that reads the clock first
  • a hang in a file whose test does a short read
  • a clocked owner beside a counted one under the work budget
  • a spin after a short async read
  • an authored mutant whose owner spins
  • a later owner's test listed first beside an earlier owner's hang (added by #182)

Proposed fix: record all 109 names in order, and make the canary also require the recorded list to equal the current list for every name that existed on main (or require exact equality on each PR that adds a history). The file is #99's to own once #99 merges; this issue exists so the stale state is visible and tracked rather than left silent.

Lenguaje dominante
JavaScript
Estrellas
5
Forks
1
Merge medio
11 h 18 min
PR fusionados (30 d)
66

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

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de TanStack/oracles

Todos los issues de TanStack/oracles

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.