Skip to content

Define cancellation ownership for detached source fills #3700

Open

Description

@kriszyp

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.

Finding IDs: f03d892c931d.

Review-Deferral: 7a8ebd642c3adef4 severity=minor category=correctness

🤖 Generated by OpenAI Codex; posted via @kriszyp.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    Priority

    P2

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions