Fix incorrect subparser, missing exception guards (release 2.8.2) #262
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
why-not-try-calmer
changed the title
why-not-try-calmer
force-pushed
the
fixing-wrong-subparser-missing-exceptions
branch
2 times, most recently
from
a1ef32b to
a1cc9dd
Compare
why-not-try-calmer
force-pushed
the
fixing-wrong-subparser-missing-exceptions
branch
from
a1cc9dd to
c2b5b75
Compare
why-not-try-calmer
force-pushed
the
fixing-wrong-subparser-missing-exceptions
branch
from
0e66f05 to
dc7b521
Compare
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.
Was notified that CIs are choking on the
no_validationflag. Here is the fix. This went unnoticed in tests as the tests don't use the particular parser/subparser structure as the code base.