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

Ouverte
#183 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
2/5
Temps estimé
1-3 heures
Accessibilité débutants
55/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
javascript, node.js
Domaine
testing

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
JavaScript
Étoiles
5
Forks
1
Merge moyen
11 h 18 min
PR mergées (30 j)
66

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

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de TanStack/oracles

Toutes les issues de TanStack/oracles

Issues similaires

Plus d'issues JavaScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.