Fix infinite loop when parsing invalid flags for apps with short option handling #911
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 old implementation of iterative parsing assumed that the error messages returned from the
flag
library would come in like this:It turns out the error message for both is
flag provided but not defined: -invalid
.This faulty assumption meant the iterative flag-parsing logic used for short-option handling could get into an infinite loop, where the same arguments would be parsed each loop, producing the same error each time with no exit condition.
To reproduce:
The following will hang forever, as will any flag prefixed by
--
:The new test cases now cover that scenario.
I also cleaned up the arg rebuilding logic a bit to avoid unnecessary appends and loop iterations, and I added a condition to guarantee that an infinite loop cannot occur for any reason in the future, even though that code path should theoretically be unreachable as it stands.