Skip to content

bug: fence late quarantine reports after rejected lane reuse #404

Closed

Description

@danny-avila

A late quarantine report for a rejected assignment can replace a successor assignment’s workspace fence after #401 releases the original fence.

Reproduced through RedisWorkspaceRequests and RedisBridgeStore:

  1. Register a two-slot worker with linked-worktree lane support.
  2. Queue two requests on the same lane and lease assignment A.
  3. A settles as rejected, without a local-cleanup acknowledgment. Its fence is released.
  4. Reconcile and lease successor assignment B; the lane fence contains B’s assignment ID.
  5. A reports quarantine using its still-valid ownership receipt (settle(..., quarantine=true)).
  6. The lane fence changes from B’s ID to quarantined:<A>.

A focused Bun regression test reproduced this deterministically: the final assertion expected B’s assignment ID and received A’s quarantine marker.

quarantineSettledWorkspace() checks receipt metadata, incarnation, identity, and reset epoch, but its quarantine branch writes the fence unconditionally unless both localCleanup and resultCommitted are set. Normal successor admission retains the reset epoch, so that check does not fence A. A run can report quarantine after guard cleanup/cleanup acknowledgment fails, so this is reachable after a committed rejection.

Acceptance:

  • Prevent a released assignment’s late quarantine from replacing a successor’s fence, including after the successor completes.
  • Retain quarantine for an uncertain current owner and make its receipt retries idempotent.
  • Preserve reset-epoch and worker-incarnation fencing.
  • Add a transition test covering rejected A → admitted B → late quarantine A.

Related: #401 and #402. This is separate from PDF extraction issue #403.

Activity

  1. danny-avila commented on Nov 17, 2026

    @danny-avila
    CollaboratorAuthor

    Fix published in #407. Admission now advances the ownership epoch, so older receipts cannot quarantine a successor or its completed workspace. The regression covers active/completed/quarantined successors and legacy receipts; 86 local tests, nine focused real-Redis cases, and the service build pass. CI and exact-head review are running.

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

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions