reach: a timed-out run reused after an edit depends on timeouts, so its coverage is no longer required (#90)

Aperta
#104 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
20/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
javascript
Ambito
testing

Direzione di ricerca

Start in the witness module's edit sequence (an edit sequence over the witness module) and find where PR #90 dropped the state a timed-out run reused after an edit. Look at its predicate daemon.evidence.cut < coldRun.evidence.cut, then at how the CLI assigns cut counts, and compare with the #84 fix for the heartbeat state. Done means the cut comes from a recorded count rather than wall-clock timeouts, so the state can be required again and the witness unit passes deterministically. Run the witness unit test to confirm.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

PR #90 removed the reach state a timed-out run reused after an edit from the witness module's edit sequence. Its predicate compares the cut counts of a daemon check and a cold run (daemon.evidence.cut < coldRun.evidence.cut), and those counts depend on wall-clock timeouts. Determinism failed on the witness unit because the state was present in one run and not the other.

The state is no longer observed, required, or entered by its constructed history (an edit sequence over the witness module). That is a coverage loss: nothing now claims that the daemon reuses a timed-out run after an edit. Law 9 is still judged on the outcomes of that history, since the comparison runs on every check.

What restores it

A deterministic cut: the witness's hang is cut by a count the CLI records (for example, a call budget or an owner's run count), not by the clock. With that, the state's predicate depends only on the history, and the state can be observed and required again. #84 is the same kind of fix for the heartbeat state.

Authority

Register (2026-11-14): "Determinism under load covers witnesses too: an oracle driver must not rely on wall-clock ordering." The evidence counts are not observed, as for cli (note in the stability check).

Lingua principale
JavaScript
Stelle
5
Fork
1
Merge medio
8h 31m
PR unite (30g)
60

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di TanStack/oracles

Tutte le issue di TanStack/oracles

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.