mirror of
https://github.com/stablyai/orca.git
synced 2026-11-19 04:23:57 +00:00
* fix(worktree): bound teardown RPCs so Windows workspace deletion can't hang Native-Windows workspace deletion failed with "Timed out waiting for physical PTY teardown". On win32 the daemon PTY adapter is the local provider, and destructive teardown's kill/listSessions RPCs used the DaemonClient 30s default — larger than the 10s sweep deadline — so a slow/wedged daemon let the outer deadline fire with the confusing error and blocked deletion. Thread an optional `timeoutMs` through IPtyProvider.shutdown/listProcesses and bound every RPC on the destructive-removal path (provider sweep, registry sweep, and the runtime-graph sweep via stopAndWait) to the remaining sweep budget minus a margin. The daemon adapter shares one budget across ensureConnected + the RPC; the SSH provider forwards the bound to the relay mux. stopAndWait splits the budget across its two sequential RPCs and bounds the cold-start wait, failing closed. Result: a wedged backend now fails fast with the accurate "Failed to physically stop every PTY" (retry succeeds once the process is truly gone), and the misleading deadline error no longer blocks deletion. Fail-closed safety is preserved: a genuinely-live process still blocks removal. Non-teardown callers pass no timeoutMs and keep the 30s default. * refactor(worktree): thread an absolute teardown deadline instead of a relative timeout Elegance pass on the teardown-RPC bounding. Instead of passing a relative `timeoutMs` and reconstructing an absolute deadline + "remaining budget" at three layers (stopAndWait, the daemon adapter's shutdown/listProcesses, and per-RPC in the sweeps), thread one absolute `deadlineMs` (epoch ms) through IPtyProvider.shutdown/listProcesses. Each RPC leaf converts to a relative timeout exactly once, at the moment it issues (`max(1, deadlineMs - now)`). Why this is cleaner: - The threaded value's identity is a point in time, not a duration, matching the codebase's existing deadline-based shared-budget idiom. - Sequential RPCs (kill then liveness verify) share the budget structurally: a later leaf converting the same deadline naturally gets less time, so the explicit recompute-after-shutdown bookkeeping disappears. - Removes the per-layer deadline re-anchoring that let the effective deadline drift slightly later at each hop. - The 500ms margin is now applied once (`teardownRpcDeadline`), and the dead `: opts.timeoutMs` else-arms in the adapter are gone. No behavior change: non-teardown callers still pass nothing and keep the 30s default + original connect behavior; fail-closed safety is intact. Tests strengthened to pin the exact leaf-observed budgets and the margin. --------- Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>