Fixing Unarchiver treats non-zero exits as errors only on empty outputs - #78
Merged
Merged
Conversation
Author
|
Thanks for merging and your maintenance, @ChrisJefferson. |
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.
The base
Extractor.is_fatal_errorreturns False, so by default a non-zero exit is only treated as an error when no files came out. I wasn’t able to reproduce this error in a test because the current test setup doesn’t support to somehow fallback onunarinstead ofrar. But I added a test forunrar. Let me know if you would prefer me to remove this test instead.