Oracle: observe durable writes during sync-metadata read holds and abandonment

Aberta
  • Algo errado?
#2,341 1 comentário 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
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
8/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
typescript
Domínio
testing-qa

Direção de pesquisa

Start with the sync-metadata entry in docs/contributing/oracle-coverage.md, then the sync-metadata session oracle and its persisted and native receiving drivers. The work is to record durable transaction observations at the receipt boundary for read-hold and abandonment histories, independent of the production metadata classifier. Done means a parent RED trace, a repaired GREEN run, and a hostile mutant that the same comparison rejects, with exact commands and results recorded.

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

Descrição

Coverage gap

The sync-metadata session coverage entry explicitly retains this observation obligation:

The read-hold and abandonment lanes retain source-facing comparisons but do not provide the peer lanes' direct durable transaction trace. A receiving witness must stage a wrong durable write followed by repair while a read hold buffers a commit, including abandonment, and reject it at the appropriate durable boundary.

This is a recorded test-instrument gap, not a newly demonstrated production defect. The text remains in the audited main source at c5ad6ad5a782ff04e9157bdef69399f2b5ba813b.

A final source-facing or repaired durable snapshot can miss an incorrect durable write that was later undone. The receiver needs an observation at the durable boundary where that write becomes observable.

Owner and work

Keep this under the existing sync-metadata session oracle and its persisted/native receiving drivers. Preserve the accepted laws that distinguish tab-local seed metadata, explicit durable metadata writes, unknown-author recovery and buffered-commit abandonment; do not redefine durable state to agree with a source read.

  • Construct read-hold histories with a buffered commit, both eventual application and abandonment, and nearby controls.
  • Record actual durable transaction observations at the appropriate receipt/boundary, independently of the production metadata classifier.
  • Calibrate with a deliberately wrong durable write followed by repair. The same comparison must reject the transient violation even when final state agrees.
  • Require measured generated reach and fixed/random replay parity.
  • Preserve existing source-facing comparisons and budgets. Record exact commands, source bindings, results and receiving limits.

If this exposes a product failure, retain its trace and add parent RED / repaired GREEN / hostile-mutant evidence before claiming closure.

Related boundaries

#2272 tracks the broader real-coordinator/host receiving scope, including remaining transport and lifecycle cases. #2317 is a distinct source-facing controlled-notice failure. #2281 concerns row resurrection. This durable observation task does not assert a common cause or close any of those issues.

Linguagem predominante
TypeScript
Estrelas
4k
Forks
277
Merge médio
1d 9h
PRs com merge (30d)
162

Preparar o ambiente

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

Todas as issues de TanStack/db

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

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