Fix dev crashloop: session window within the 4-hour maximum
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 3m26s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 4s
Foundation / image (push) Successful in 5s

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 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-08 07:28:39 -04:00
co-authored by Claude Opus 5.5
parent b2f224d0a2
commit 4a72897679
@@ -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.