Repository navigation
fix(local): wait for PostgreSQL TCP readiness - #5
Merged
Merged
Conversation
Avoid marking the socket-only initialization server healthy before migrations start. Add a fresh-volume Docker regression test. Assisted-by: Pi
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
jiangpengcheng
approved these changes
Sep 30, 2026
This was referenced Sep 30, 2026
Merged
Merged
Merged
Merged
Merged
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changes and why
Use TCP readiness to avoid accepting PostgreSQL's temporary initialization server. Add a fresh-volume regression test; no migration retry needed.
Compatibility
No CLI or public API changes.
How I tested it
AI assistance
Pi implemented the fix and test; verified with the checks above. Human sign-off pending.