Skip to content

Wire v2: end-to-end deadlines and cancellation by request ID #173

Closed

Description

@jsam

Problem

Queue timeout and cancellation need one contract spanning admission through computation, including the durable write boundary.

Evidence

Source: 5c1f313379a5cb2995a43a66ddba0b5cc9798b7f (inspected 2026-10-03). These are source findings; the acceptance scenarios below still need implementation and execution.

Acceptance criteria

  • Carry one deadline across admission, queueing and execution; cancellation by request ID reaches queued and running work.
  • A timed-out queued operation never starts later. Running queries release resources promptly.
  • Document that durable commit cannot be cancelled midway; report committed/unknown outcomes explicitly for safe retry.
  • Test cancellation on both sides of the transaction boundary and preserve cheap-query/delta performance through Performance: baseline and mandatory pre-PR regression pipeline #163.

Delivery

Plan item: W03. R2 - Atomic programs + wire protocol.

Dependencies / related work: #172, #170.

Contributes to #132; completing this slice alone does not close the broader issue.

Activity

  1. added
    backendBackend/server related
    sdkPython, JavaScript and Rust clients and CLI
    P1Required next for reliable reactive delivery and operations
    on Oct 3, 2026
  2. jsam commented on Oct 4, 2026

    @jsam
    ContributorAuthor

    Delivered by #214 and #220 (cancel_ack, deadline_exceeded, OutcomeUnknown for non-cancellable writes); verified on main 4adce1e.

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

    P1Required next for reliable reactive delivery and operationsbackendBackend/server relatedsdkPython, JavaScript and Rust clients and CLI

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions