Ilia Denisov 06a2e631c9 fix(backend): retry migrations on transient connection errors ...

Backend e2e tests (and, more rarely, service startup) intermittently
failed applying migrations with `driver: bad connection`: a freshly
started Postgres — notably a test container — can reset a pooled
connection moments after it reports ready, killing the migration
transaction. The harness already waits for the double "ready" log and
pings before migrating, yet goose can still draw a connection postgres
then resets.

ApplyMigrations now wraps the schema-create + goose run in a bounded
retry that fires only on transient connection errors (driver.ErrBadConn
and the connection-failure messages Postgres drivers surface); both
steps are idempotent, so a retry resumes cleanly. Deterministic SQL
errors still fail fast.

Fixes the intermittent TestDiplomailAsyncFallbackOnUnsupportedPair (and
the eight other testcontainer e2e harnesses that share ApplyMigrations).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-05-30 14:45:53 +02:00

..

jet

Phase 28 (Step 1): backend support for race-name mail send

2026-05-15 22:07:48 +02:00

migrations

chore(ci): tidy CI/dev infra — drop local-ci, lift migration rule, scope by galaxy.stack label

2026-05-18 23:32:42 +02:00

migrations_test.go

diplomail (Stage A): add in-game personal mail subsystem

2026-05-15 18:28:55 +02:00

pool_test.go

fix(backend): retry migrations on transient connection errors

2026-05-30 14:45:53 +02:00

pool.go

fix(backend): retry migrations on transient connection errors

2026-05-30 14:45:53 +02:00

testopts.go

docs: reorder & testing

2026-05-07 00:58:53 +03:00