-
Notifications
You must be signed in to change notification settings - Fork 531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FIX: Improve error handling of CommandLine
interfaces
#3395
Conversation
Currently, errors arising from interpolating the command line of these interfaces is handled poorly at the ``Node`` level. If the command line cannot be built, the error is printed in the logfile but the exception is caught and never raised (i.e., likely leading to an infinite loop as the execution is not stopped). I have experienced that while debugging fMRIPrep. To learn which of the inputs of a faulty interface derived from ``CommandLine`` was not being formatted, I had to also add the error annotation proposed for the ``_parse_inputs`` inner loop.
Codecov Report
@@ Coverage Diff @@
## master #3395 +/- ##
==========================================
+ Coverage 65.20% 65.29% +0.09%
==========================================
Files 307 307
Lines 40457 40926 +469
Branches 5350 5515 +165
==========================================
+ Hits 26379 26724 +345
- Misses 13003 13102 +99
- Partials 1075 1100 +25
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fine to merge with or without my suggestion.
Oh, looks like there's a style check failing... |
Co-authored-by: Chris Markiewicz <effigies@gmail.com>
Currently, errors arising from interpolating the command line of these interfaces is handled poorly at the
Node
level.If the command line cannot be built, the error is printed in the logfile but the exception is caught and never raised (i.e., likely leading to an infinite loop as the execution is not stopped).
I have experienced that while debugging fMRIPrep. To learn which of the inputs of a faulty interface derived from
CommandLine
was not being formatted, I had to also add the error annotation proposed for the_parse_inputs
inner loop.Acknowledgment