You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
teststation listens with quic-go's 30 s idle timeout; the live station uses 300 s #62
Purpose (reliability): a test that dials macula-go's in-process teststation sees the connection lifetime a live station gives, so a test passes or fails for the reasons production would; today a 30 s path outage ends the connection in tests and not on the fleet.
Facts (v0.27.0-rc.4 and origin/master)
teststation/station.go:161 listens with &quic.Config{}: quic-go's default MaxIdleTimeout is 30 s.
The idle timeout in force is the minimum of both sides'. Clients ask for 300 s (macula-rust transport.rs IDLE_TIMEOUT, macula-go transport/profile_dial.go:192), and the live Erlang station listens with 300 s (macula_quic.erl, idle_timeout_ms default 300_000). So against the teststation every client gets 30 s.
Purpose met. The teststation now gives a connection the lifetime a live station does: a 5 minute idle timeout with keepalive PINGs. A 30 s path outage no longer ends the connection in tests.
Activity
rgfaber commentedon Oct 30, 2026
Purpose met. The teststation now gives a connection the lifetime a live station does: a 5 minute idle timeout with keepalive PINGs. A 30 s path outage no longer ends the connection in tests.
Evidence: