Skip to content

Commit 4948f20

Browse files
committed
🤖 Fix SSH exec timeout with ControlMaster socket reuse
## Problem SSH commands with timeout could run indefinitely on remote hosts despite client-side timeouts. When ControlMaster multiplexing was enabled, killing the local SSH client didn't terminate the remote command—it continued running under the shared master connection. ## Solution **Three-layer timeout protection:** 1. **Client-side timeout** - SIGKILL after timeout expires (immediate local cleanup) 2. **Remote-side timeout** - Wrap commands with `timeout -s KILL` utility 3. **SSH connection timeout** - ConnectTimeout + ServerAlive* options Remote timeout is set to `timeout + 1s` to ensure local timeout normally fires first for cleaner error handling. Uses BusyBox-compatible syntax (`-s KILL`) for Alpine Linux compatibility. **ControlMaster always enabled** - Socket reuse now works for all operations, including timed commands. This preserves 50-200ms performance savings per operation from connection pooling. ## Testing - Added timeout integration test for both local and SSH runtimes - Verifies `sleep 10` with 1s timeout completes in ~1s (not 10s) - All 88 integration tests pass - 807 unit tests pass (4 pre-existing gitService failures unrelated) ## Impact Commands with timeout now properly terminate on remote hosts while maintaining the performance benefits of SSH connection multiplexing.
1 parent 71e965c commit 4948f20

File tree

2 files changed

+59
-9
lines changed

2 files changed

+59
-9
lines changed

src/runtime/SSHRuntime.ts

Lines changed: 36 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -98,10 +98,19 @@ export class SSHRuntime implements Runtime {
9898
parts.push(command);
9999

100100
// Join all parts with && to ensure each step succeeds before continuing
101-
const fullCommand = parts.join(" && ");
101+
let fullCommand = parts.join(" && ");
102+
103+
// Wrap remote command with timeout to ensure the command is killed on the remote side
104+
// even if the local SSH client is killed but the ControlMaster connection persists
105+
// Use timeout command with KILL signal
106+
// Set remote timeout slightly longer (+1s) than local timeout to ensure
107+
// the local timeout fires first in normal cases (for cleaner error handling)
108+
// Note: Using BusyBox-compatible syntax (-s KILL) which also works with GNU timeout
109+
const remoteTimeout = Math.ceil(options.timeout) + 1;
110+
fullCommand = `timeout -s KILL ${remoteTimeout} bash -c ${shescape.quote(fullCommand)}`;
102111

103112
// Wrap in bash -c with shescape for safe shell execution
104-
const remoteCommand = `bash -c ${shescape.quote(fullCommand)}`;
113+
const remoteCommand = fullCommand;
105114

106115
// Build SSH args
107116
const sshArgs: string[] = ["-T"];
@@ -125,10 +134,30 @@ export class SSHRuntime implements Runtime {
125134
// ControlMaster=auto: Create master connection if none exists, otherwise reuse
126135
// ControlPath: Unix socket path for multiplexing
127136
// ControlPersist=60: Keep master connection alive for 60s after last session
137+
//
138+
// Socket reuse is safe even with timeouts because:
139+
// - Each SSH command gets its own channel within the multiplexed connection
140+
// - SIGKILL on the client immediately closes that channel
141+
// - Remote sshd terminates the command when the channel closes
142+
// - Multiplexing only shares the TCP connection, not command lifetime
128143
sshArgs.push("-o", "ControlMaster=auto");
129144
sshArgs.push("-o", `ControlPath=${this.controlPath}`);
130145
sshArgs.push("-o", "ControlPersist=60");
131146

147+
// Set comprehensive timeout options to ensure SSH respects the timeout
148+
// ConnectTimeout: Maximum time to wait for connection establishment (DNS, TCP handshake, SSH auth)
149+
// ServerAliveInterval: Send keepalive every 5 seconds to detect dead connections
150+
// ServerAliveCountMax: Consider connection dead after 2 missed keepalives (10 seconds total)
151+
// Together these ensure that:
152+
// 1. Connection establishment can't hang indefinitely
153+
// 2. Established connections that die are detected quickly
154+
// 3. The overall timeout is respected from the moment ssh command starts
155+
// Use the configured timeout for connection establishment
156+
sshArgs.push("-o", `ConnectTimeout=${Math.ceil(options.timeout)}`);
157+
// Set aggressive keepalives to detect dead connections
158+
sshArgs.push("-o", "ServerAliveInterval=5");
159+
sshArgs.push("-o", "ServerAliveCountMax=2");
160+
132161
sshArgs.push(this.config.host, remoteCommand);
133162

134163
// Debug: log the actual SSH command being executed
@@ -175,16 +204,14 @@ export class SSHRuntime implements Runtime {
175204

176205
// Handle abort signal
177206
if (options.abortSignal) {
178-
options.abortSignal.addEventListener("abort", () => sshProcess.kill());
207+
options.abortSignal.addEventListener("abort", () => sshProcess.kill("SIGKILL"));
179208
}
180209

181210
// Handle timeout
182-
if (options.timeout !== undefined) {
183-
setTimeout(() => {
184-
timedOut = true;
185-
sshProcess.kill();
186-
}, options.timeout * 1000);
187-
}
211+
setTimeout(() => {
212+
timedOut = true;
213+
sshProcess.kill("SIGKILL");
214+
}, options.timeout * 1000);
188215

189216
return { stdout, stderr, stdin, exitCode, duration };
190217
}

tests/runtime/runtime.test.ts

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -142,6 +142,29 @@ describeIntegration("Runtime integration tests", () => {
142142

143143
expect(result.stdout.trim()).toContain(workspace.path);
144144
});
145+
test.concurrent(
146+
"handles timeout correctly",
147+
async () => {
148+
const runtime = createRuntime();
149+
await using workspace = await TestWorkspace.create(runtime, type);
150+
151+
// Command that sleeps longer than timeout
152+
const startTime = performance.now();
153+
const result = await execBuffered(runtime, "sleep 10", {
154+
cwd: workspace.path,
155+
timeout: 1, // 1 second timeout
156+
});
157+
const duration = performance.now() - startTime;
158+
159+
// Exit code should be EXIT_CODE_TIMEOUT (-998)
160+
expect(result.exitCode).toBe(-998);
161+
// Should complete in around 1 second, not 10 seconds
162+
// Allow some margin for overhead (especially on SSH)
163+
expect(duration).toBeLessThan(3000); // 3 seconds max
164+
expect(duration).toBeGreaterThan(500); // At least 0.5 seconds
165+
},
166+
15000
167+
); // 15 second timeout for test (includes workspace creation overhead)
145168
});
146169

147170
describe("readFile() - File reading", () => {

0 commit comments

Comments
 (0)