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
Add owner-authenticated cancellation for one app registration #63
The revised boundary is tracked in #23: an accepted heartbeat that removes an app begins a bounded drain owned and enforced by Node. Node stops new admission/discovery, preserves existing work until completion or the first deadline, and performs normal session/payment/request/proxy/channel teardown at expiry. Runtime observes the result through heartbeats and stages workload replacement.
The original purpose of this ticket was for Runtime to enforce its own drain timer and then call an owner-authenticated POST /runners/{runner_id}/apps/{app_id}/cancel without session tokens. That operation is no longer required for the maintenance/upgrade flow: Node already owns the sessions it must end. No separate immediate force-cancel use case has been established for this ticket.
Runtime's per-app cancellation request/reservation plumbing has also been removed from the inspected Control Center source at a16883b. The native SDK and Node-owned drain integration still require Drain withdrawn apps in Node with a bounded deadline #23, SDK #7 and Runtime #94. Closing this superseded proposal does not claim those replacements are complete.
Closing as superseded / not planned. Integrated acceptance remains in naap-ops #118.
Activity