From 4a72897679f7029cafe841678a733cfbd8524728 Mon Sep 17 00:00:00 2001 From: dingo Date: Thu, 8 Oct 2026 07:28:39 -0400 Subject: [PATCH] Fix dev crashloop: session window within the 4-hour maximum b2f224d set REGION_SESSION_WINDOW to expire about 5.2 hours after the pod started; evo-server refuses windows longer than 4 hours (SessionWindow::max_duration_seconds) and exited with "error m10-window-too-long" in a loop. The window now expires 3 h 50 min after it was written. Co-Authored-By: Claude Opus 5.5 --- deploy/kubernetes/region/dev-session-route/listener.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy/kubernetes/region/dev-session-route/listener.yaml b/deploy/kubernetes/region/dev-session-route/listener.yaml index 3d3d2cb..eee9882 100644 --- a/deploy/kubernetes/region/dev-session-route/listener.yaml +++ b/deploy/kubernetes/region/dev-session-route/listener.yaml @@ -12,7 +12,7 @@ spec: env: - {name: REGION_SESSION, value: "dev"} - {name: REGION_SESSION_LISTEN, value: "0.0.0.0:7400"} - - {name: REGION_SESSION_WINDOW, value: "dev-20261008T111342-32432:1791477222"} + - {name: REGION_SESSION_WINDOW, value: "dev-20261008T112240-4ebe:1791472360"} - {name: REGION_M10_MAX_GRANT_LIFETIME, value: "14400"} ports: # QUIC (ADR-0090): UDP only; nothing listens on TCP 7400.