Repository navigation
fix(ci): stabilize database and peer readiness - #56
Merged
Merged
Conversation
xiaoland
changed the title
xiaoland
marked this pull request as ready for review
August 13, 2026 15:50
This branch was previously deployed
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.
Main admission and the follow-up preview exposed two readiness races.
pg_isready, which could succeed against PostgreSQL's temporary initialization server before the target database and final TCP listener existed. It now waits by executingSELECT 1through the exact TCP/database path used by restore.Validation:
git diff --checkpdm run pytest tests/deployment/test_configure_peer_runtime.py -qpdm run pre-commit run --files .github/workflows/ci.yml scripts/configure_peer_runtime.py