feat(sandbox): wall-clock timeout watcher and ownership reaper law #21

Open
opened 2026-09-09 10:15:32 +00:00 by larandar · 0 comments
Owner

Proposal

Terminate timed-out runs safely using wall-clock deadlines and proven ownership.

Design

Apply instance.nu ownership law: SIGTERM proven run PIDs, wait five seconds, then SIGKILL remaining owned PIDs.

Tasks

  • Track deadlines; validate ownership; implement escalation; report timeout state.

Gherkin Specification Delta

must.contracts.ting-workflows.deliverable-21

Scenario: Deliverable behavior

  • GIVEN the stated prerequisites and inputs
  • WHEN the feature is exercised
  • THEN an owned run exceeding deadline, when watcher fires, then only proven PIDs are signaled and escalation occurs after five seconds.
## Proposal Terminate timed-out runs safely using wall-clock deadlines and proven ownership. ## Design Apply instance.nu ownership law: SIGTERM proven run PIDs, wait five seconds, then SIGKILL remaining owned PIDs. ## Tasks - Track deadlines; validate ownership; implement escalation; report timeout state. ## Gherkin Specification Delta ### must.contracts.ting-workflows.deliverable-21 **Scenario: Deliverable behavior** - **GIVEN** the stated prerequisites and inputs - **WHEN** the feature is exercised - **THEN** an owned run exceeding deadline, when watcher fires, then only proven PIDs are signaled and escalation occurs after five seconds.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
Ting/workflows#21
No description provided.