Return a proper exit code if an error occurs#65
Merged
mla merged 1 commit intomla:masterfrom Mar 30, 2025
Merged
Conversation
Owner
|
Ty Kevin! Will review this weekend |
Owner
|
Merged. I simplified it a bit, I think... let me know if u see any prob with that. thx again |
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
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.
My perl is super rusty so I'm not sure if this is the best way to do this.
We had an issue recently where pg_sample encountered an error and exited. Unfortunately the END block does
exit 0;so our script that runs pg_sample thought that it had finished successfully and continued on. To fix this I've added a$SIG{__DIE__}handler that records the error to@reason. Then in the END block I check if@reasonis set and if so exit with code 1 to signify an error occurred.