mirror of
https://github.com/PerpetualSoftware/pad.git
synced 2026-10-03 20:20:29 +00:00
xarmian
a061c17298
The health test's load-bearing assertion is that an unreachable Redis leaves /health/ready at 200 — a test that only checked the payload would pass against a handler that also 503'd, which is exactly the regression that would pull healthy replicas out of a load balancer over a degraded feature. Each test asserts its own premise first: no redis block without a prober, nothing reported before Start, healthy presence operations reporting zero failures. Without those legs an always-reporting implementation would be indistinguishable from a correct one. Both suites bound DialTimeout explicitly. go-redis does not apply a command context to connection establishment, so the unreachable legs would otherwise wait out the 5s default per probe. Claude-Session: https://claude.ai/code/session_01JVDBKbgn3Xt7ndW1YoYd8X