Gap CLI: a partial or daemon run can draw other drawn bases than a cold run without --seed

Ouverte
#155 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é
4/5
Temps estimé
3-5 jours
Accessibilité débutants
48/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
javascript, node.js
Domaine
testing

Piste de recherche

Start with src/oracle-config.ts and oracle-gaps/capture-setup.mjs, then find the gap CLI paths for cold, partial, and daemon checks. First reproduce the mismatch with a property whose history has drawnBases and no --seed; the issue says the repository’s current gap e2e and self-oracles do not provide a suitable witness. Done means a gap report establishes whether the drawn bases differ and, if they do, the CLI produces order independent bases.

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

Description

In the gap CLI, a property's drawn bases (#122, histories.drawnBases) can differ between a cold whole-file run and a partial or daemon run, when the CLI runs with no --seed. Found by reading (review of #122, round 2, G6). It is not reproduced yet.

  • Where R comes from: a fixed-seed constructed unit draws its drawn bases from R + k. R is the run's random seed: the first unit that uses it draws it from Math.random, through oracleCampaignSeed (src/oracle-config.ts).
  • The capture: it seeds Math.random per test, by the test's key (oracle-gaps/capture-setup.mjs, installRandom). So R is a function of which test is the first to call runSeed in that process.
  • The failure: in a cold whole-file run, that is the property's first drawing fixed-seed unit. If a partial run, a daemon check, or a batch copy runs a set of tests whose first drawing unit is a different one, it draws another R. A later unit's drawn bases then differ from the baseline's. Then:
    • unchanged code can read as changed (a false kill, or not-judged);
    • a verdict on a drawn base can be credited on the fixed seed route (a reproducible route, P3, G2, I8) when a cold run doesn't repeat it.
  • Not affected: with --seed, ${envPrefix}_SEED fixes R in every run, and the drawn bases are the same.
  • In this repository today: the gap e2e oracle and the self-oracle draw bases (1 each, and the e2e oracle draws none on win32). No oracle that the gap CLI judges in CI draws bases.

Ask, oracle-first:

  1. A gap-report witness: a property with drawnBases, judged cold and through the daemon (or partially) with no --seed. It should show whether the classes match.
  2. If they differ, a fix that makes R independent of test order inside the CLI. For example, the CLI could always set ${envPrefix}_SEED for a check, choosing and printing one when --seed is absent. Or it could seed oracleCampaignSeed's draw from the property id rather than from the first test's key.

This issue was written by Isaac.

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.