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

Aberta
#104 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
20/100
Tipo de issue
Bug
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
javascript
Domínio
testing

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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).

Linguagem predominante
JavaScript
Estrelas
5
Forks
1
Merge médio
8h 31min
PRs com merge (30d)
60

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de TanStack/oracles

Todas as issues de TanStack/oracles

Issues semelhantes

Mais issues de JavaScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.