fix: surface vault-init postgres connection errors and reduce CI timeout risk - #41
Merged
Merged
Conversation
…out risk The "Run Tests" CI job has been failing consistently (both before and after 3f896ce) with vault-init exiting 1 after ~60-70s, but the real psql error was swallowed (`> /dev/null 2>&1`), leaving only a bare exit code in the logs. wait_for_postgres now surfaces the last psql error on timeout, the timeout budget is bumped to 120s, and vault-init-dependencies.sh runs a single `apk update` instead of three, shaving time off before the postgres wait even starts.
Neopallium
approved these changes
Jul 22, 2026
F-OBrien
approved these changes
Jul 22, 2026
Collaborator
Author
|
/fast-forward |
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
4 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.
Description
The "Run Tests" CI job has been failing consistently (both before and after 3f896ce) with vault-init exiting 1 after ~60-70s, but the real psql error was swallowed (
> /dev/null 2>&1), leaving only a bare exit code in the logs. wait_for_postgres now surfaces the last psql error on timeout, the timeout budget is bumped to 120s, and vault-init-dependencies.sh runs a singleapk updateinstead of three, shaving time off before the postgres wait even starts.