From 4d569c22b44d0bceca2a68045650a2c29fe114ae Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabiano=20Fid=C3=AAncio?= Date: Sun, 7 Jun 2026 13:04:20 +0200 Subject: [PATCH] runtime-rs: enforce a minimum vsock reconnect window MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Low-CPU sandboxes can take longer than a few seconds to complete guest boot and start the agent. Let's clamp the reconnect timeout to a safe minimum so sandbox startup does not fail early with transient vsock ECONNRESET. Signed-off-by: Fabiano Fidêncio Assisted-by: Codex --- src/runtime-rs/crates/agent/src/sock/mod.rs | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/src/runtime-rs/crates/agent/src/sock/mod.rs b/src/runtime-rs/crates/agent/src/sock/mod.rs index a82da79072..54549660fb 100644 --- a/src/runtime-rs/crates/agent/src/sock/mod.rs +++ b/src/runtime-rs/crates/agent/src/sock/mod.rs @@ -90,9 +90,14 @@ pub struct ConnectConfig { impl ConnectConfig { pub fn new(dial_timeout_ms: u64, reconnect_timeout_ms: u64) -> Self { + // With static sandbox resource sizing enabled by default, tiny CPU + // allocations can make early guest boot/agent startup exceed 3s on + // loaded nodes. Keep a reasonable lower bound to avoid premature + // sandbox teardown during agent bring-up. + const MIN_RECONNECT_TIMEOUT_MS: u64 = 10_000; Self { dial_timeout_ms, - reconnect_timeout_ms, + reconnect_timeout_ms: reconnect_timeout_ms.max(MIN_RECONNECT_TIMEOUT_MS), } } }