fix: use robust wait strategy for postgres testcontainers #888
+20
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Replace wait.ForListeningPort with wait.ForAll combining ForLog and ForListeningPort. PostgreSQL opens the TCP port before initialization completes, causing "connection reset by peer" errors. The log message appears twice (once during initdb, once after restart), so WithOccurrence(2) ensures full readiness before tests connect.
owen-eth
approved these changes
Feb 10, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replace wait.ForListeningPort with wait.ForAll combining ForLog and ForListeningPort. PostgreSQL opens the TCP port before initialization completes, causing "connection reset by peer" errors. The log message appears twice (once during initdb, once after restart), so WithOccurrence(2) ensures full readiness before tests connect.