Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

offline-transactions interruption oracle fails when a random sample misses a landing

Ouverte
  • Quelque chose ne va pas ?
#2,142 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é
3/5
Temps estimé
Une demi-journée
Accessibilité débutants
62/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
typescript
Domaine
testing

Piste de recherche

Start with packages/offline-transactions/tests/interruption-settlement-oracle.property.test.ts, where the failing assertion compares the landings reached by a random sample with the full landing list. Run the test several times to reproduce the intermittent failure. Done means the coverage check no longer depends on random sampling (either fixed named histories per landing, or moved to the fixed-seed campaign), and the random law check still runs and passes repeatedly.

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

Description

Summary

packages/offline-transactions/tests/interruption-settlement-oracle.property.test.ts fails at random. The failing check asserts that the random histories cover every interruption landing. It is not a behavior check. When a run draws no history that reaches a refused landing, the test fails.

Failure

The test "keeps settlement and ownership for an interruption at any microtask turn" fails with:

AssertionError: interruption landings: expected [ 'dispose issued', …(5) ] to deeply equal [ 'dispose issued', …(7) ]
-   "dispose refused",
-   "leadership refused",

It failed CI on #2128, which does not change offline-transactions. CI ran it because it tests the pull request merged with main. On main (cd92156d6), 1 of 3 local runs failed the same way.

Cause

The check compares the landings that one random sample reached with the full set of landings. A sample of config.runs histories does not always reach every landing, especially the refused ones. Any run that misses one fails, even when every history it does run satisfies the law.

Suggested fix

  • Prove coverage with fixed, named histories (one per landing), not with a random sample.
  • Or move the coverage check to the fixed-seed campaign only, where the sample is deterministic.
  • Keep the random campaign for the settlement and ownership law itself.
Langage dominant
TypeScript
Étoiles
3.9k
Forks
272
Merge moyen
1 j 1 h
PR mergées (30 j)
235

Préparer son environnement

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/db

Toutes les issues de TanStack/db

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

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