test(api): let a shutdown's closed connections leave pg_stat_activity #100

Merged

Zayin_Admin merged 2 commits from fix/flaky-shutdown-connection-check into main

2026-10-14 04:41:38 +00:00

Author	SHA1	Message	Date
Zayin_Admin	bef516796e	Merge branch 'main' into fix/flaky-shutdown-connection-check CI / verify (pull_request) Successful in 1m14s Details CI / infrastructure-smoke (pull_request) Successful in 40s Details CI / package-release (pull_request) Successful in 50s Details CI / migration-smoke (pull_request) Successful in 2m24s Details CI / image-build (pull_request) Successful in 1m2s Details CI / deploy-smoke (same-origin) (pull_request) Successful in 45s Details CI / package-publication (pull_request) Successful in 58s Details CI / deploy-smoke (split) (pull_request) Successful in 2m36s Details	2026-10-14 04:23:11 +00:00
ekklesiaandClaude Opus 5.5	f2fc069e66	test(api): let a shutdown's closed connections leave pg_stat_activity CI / verify (pull_request) Successful in 1m16s Details CI / infrastructure-smoke (pull_request) Successful in 40s Details CI / package-release (pull_request) Successful in 57s Details CI / image-build (pull_request) Successful in 1m1s Details CI / migration-smoke (pull_request) Successful in 2m30s Details CI / deploy-smoke (same-origin) (pull_request) Successful in 50s Details CI / package-publication (pull_request) Successful in 55s Details CI / deploy-smoke (split) (pull_request) Successful in 2m41s Details Four integration tests shut the API down and immediately count the database's rows in pg_stat_activity, expecting zero. PostgreSQL ends a backend asynchronously: pool.end() resolves once the client side has closed, and the server can still list that backend for a moment. On a loaded runner an immediate count saw one, failing migration-smoke on a docs-only PR (Ekklesia CI run #238, module-database.integration.ts:764, "expected 1 to be +0"). Reproduced against postgres:18.4-alpine3.24 limited to 0.05 CPU: after pool.end() resolved, the backend was still listed in 7 of 300 trials, and gone about a millisecond later. The checks now wait up to 3 s for the count to reach zero. A connection that is genuinely left open is still caught: an idle pooled client stays listed for pg-pool's 10 s idle timeout, far past the deadline. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-13 23:13:21 -05:00