BF: if early attempt to parse resulted in error, setup subparsers#6980
Conversation
|
wow this hit some nerve: I guess I or someone else would need to look into it in greater depth :-/ edit : with a sober eye -- all those FAILs simply can't relate to the change since have nothing to do with the parser -- what was going on? |
ded5eec to
3a2f66f
Compare
|
I triggered a rerun of the failed appveyor runs to get a sense of whether the widespread errors are a consequence of some service failure. Re fix: Superficially, this makes sense. Even though I did the last RF of this code, it is hard for me to say "OK" with confidence. The last RF was focused on making things faster, but it certainly did not aim for (or achieve) an improvement of this code's comprehensibility. |
|
bad news: somehow all those FAILED are "real". good news: |
3a2f66f to
a7ca741
Compare
Without that using a short option for a command which is also present on top level results in early attempt error and then no parsers even tried, thus giving that error from the main/top parser to the user Fixes 6814 Regression was introduced in 0b4937d
a7ca741 to
9b21010
Compare
|
gy gy - it was the new test I added. I didn't realize that |
Codecov Report
@@ Coverage Diff @@
## maint #6980 +/- ##
==========================================
+ Coverage 90.14% 91.13% +0.99%
==========================================
Files 354 354
Lines 46321 46325 +4
Branches 6612 6612
==========================================
+ Hits 41754 42218 +464
+ Misses 4551 4091 -460
Partials 16 16
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
|
the only fail travis is a known #4496 (comment) . As @mih gives some support in the fix ("makes sense") , we have a unittest for it now, and it seems nothing breaks -- I will proceed with merge since unlikely we would get a better fix (if there is one possible) any time soon . |
|
🚀 PR was released in |
Without that using a short option for a command which is also
present on top level results in early attempt error and then no
parsers even tried, thus giving that error from the main/top parser to the user
Fixes #6814
Regression was introduced in 0b4937d ( AKA 0.16.0^2
68^217 )I have not investigated possible impact on completion etc, but when tried - still worked fine.