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

Đang mở
  • Có gì không ổn?
#2,341 1 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
5/5
Thời gian dự kiến
Hơn một tuần
Mức phù hợp với người mới
8/100
Loại issue
Tính năng
Độ rõ ràng
Khá rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
typescript
Lĩnh vực
testing-qa

Hướng nghiên cứu

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.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

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.

Ngôn ngữ chính
TypeScript
Star
4k
Fork
277
Merge trung bình
1 ngày 7 giờ
Pull request đã merge (30 ngày)
176

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của TanStack/db

Tất cả issue của TanStack/db

Issue tương tự

Thêm issue về TypeScript

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.