Disable default output error for EXPIRATION_EARLY #60
Conversation
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
This patch extends the disabling of an output error associated to EXPIRATION_EARLY that is currently enjoyed only when a configuration file is passed. In other terms, when no configuration file is set, any error is returned as error code 1. This change makes the script backwards compatible with a previous version of the client, e.g. the client in version 0.17 had this behaviour.
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.
This patch extends the disabling of an output error associated to
EXPIRATION_EARLYthat is currently enjoyed only when a configuration file is passed. In other terms, when no configuration file is set, any error is returned as error code 1.This change makes the script backwards compatible with a previous version of the client, e.g. the client in version 0.17 had this behaviour.