Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Cerrado
  • ¿Algo no está bien?
#2,142 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Ya se ha fusionado un pull request relacionado.

  • #2144 de @KyleAMathews — fusionado

Evaluación

Dificultad
3/5
Tiempo estimado
Medio día
Aptitud para principiantes
62/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
testing

Línea de trabajo

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.

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

Descripción

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.
Lenguaje dominante
TypeScript
Estrellas
3.9k
Forks
272
Merge medio
1 d 21 min
PR fusionados (30 d)
241

Preparar el entorno

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

Todos los issues de TanStack/db

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.