Fix a potential crash when UsageError is thrown
#18
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
kylef
added a commit
that referenced
this pull request
Jan 4, 2016
Fix a potential crash when `UsageError` is thrown
|
Could you tag a new version containing this fix? I just ran into this on Linux. |
Closed
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.
See neonichu/Azkaban#4
I'm not 100% sure why it is happening, but assuming that the string interpolation of
ErrorTypedoes something special, as it does not officially implementStringLiteralConvertible. According to the BT,descriptionwill still be called onUsageError, but the ivars suffer some memory corruption, leading to the crash.