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

Offen
  • Stimmt etwas nicht?
#2,341 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
8/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
testing-qa

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
TypeScript
Sterne
4k
Forks
277
Ø Merge
1 T. 9 Std.
Gemergte PRs (30 T.)
162

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus TanStack/db

Alle Issues in TanStack/db

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.