packer clean ups and better logging#2183
Open
mmlb wants to merge 4 commits into
Open
Conversation
This is currently a no-op as we are already using nixfmt-rfc-style. This also means we can drop the perSystem definition to a simple attrset which causes a reformat.
mmlb
changed the title
PostgreSQL Extension Dependency Analysis: PR #2183
SummaryNo extensions had dependencies with MAJOR version updates. Full Analysis ResultsPostgreSQL 15 Extension DependenciesPostgreSQL 17 Extension DependenciesOrioleDB 17 Extension Dependencies |
Contributor
Author
|
Best reviewed each-commit-at-a-time. |
mmlb
force-pushed
the
manny/psql-1276-investigate-ebssurrogate-exiting-with-123-error-value
branch
2 times, most recently
from
1aa2eba to
0f40205
Compare
PostgreSQL Package Dependency Analysis: PR #2183
SummaryNo packages had MAJOR version updates. Full Analysis ResultsPostgreSQL 15 Dependency ChangesExtracting PostgreSQL 15 dependencies...
Runtime Closure Size
Raw Dependency ClosurePostgreSQL 17 Dependency ChangesExtracting PostgreSQL 17 dependencies...
Runtime Closure Size
Raw Dependency Closure |
mmlb
force-pushed
the
manny/psql-1276-investigate-ebssurrogate-exiting-with-123-error-value
branch
3 times, most recently
from
9ef4252 to
6859bef
Compare
We have a bunch of scripts, mixing tabs/spaces and other things is a pain that has long been solved, lets join the club.
I was trying to debug AMI builds failing in CI where it was dying in the cleanup phase. I did this to debug the issue and have not seen it trigger again. I want to leave this in since its helpful if/when there's an error in the script again.
mmlb
force-pushed
the
manny/psql-1276-investigate-ebssurrogate-exiting-with-123-error-value
branch
from
6859bef to
74a49bf
Compare
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
1 participant
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 kind of change does this PR introduce?
Simple commit for better CI logs
What is the current behavior?
This was all in service of fixing AMI build failures, for example: https://github.com/supabase/postgres/actions/runs/26757788681/job/78981563652#step:9:6046. Similar to #2177, but looks like its still biting.
What is the new behavior?
I was trying to debug the issue and wanted to have
set -xin the clean up scripts but when I tried building the AMI again it all worked. So I want to leave this in since its helpful if/when there's an error in the script again.