Returning stderr when gpg encrypt fails #762
Merged
Conversation
This file contains 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
v3.6.1 - develop -> master
|
Can you make this merge to |
|
@autrilla done. thanks for taking a look. |
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.
We have been having a lot of trouble investigating some failures that seem to be very flaky on a few of our projects where we use sops as a library. All we see is a message that looks like the following:
This verbose error message will hopefully be more helpful to investigate and fix the underlying issue. The current error
GPG binary error: exit status 2does not give too many details today and has been making it virtually impossible to understand the failure on a CI machine that we might or might not have access to.