You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Define cancellation ownership for detached source fills #3700
Deferred from the closing review of #3527 for declarative sharding (Pro #980). The owner explicitly scoped this root cause out of the closing implementation batch.
Current assessment: Detached cache-fill cancellation is a separate lifecycle extension; late request reads already stop at the logical-transaction guard.
Owning path:resources/Table.ts. Review lines move as the companion branches integrate main; use the linked PR's current source.
Follow-up: Establish the boundary with a focused regression or code trace, then propose the smallest change consistent with the stated recovery and compatibility contracts.
This issue does not reopen #980's approved primary-key-only scope, complete-history requirement, or ban on write serialization. It does not block the current drafts. No release or backport is committed; milestone is intentionally unset. Found through source review and synthetic tests; there is no customer-specific incident evidence.
Triage: P2; effort Medium; type Task. Contained diagnostic/lifecycle investigation; no demonstrated data loss.
Activity