-
Notifications
You must be signed in to change notification settings - Fork 533
Difficult time to deal with crash files from different nipype versions #2625
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
Milestone
Comments
@anibalsolon could you show an example traceback of opening a crashfile generated by a different nipype version? |
Hi @mgxd , sure! This is an error generated on Nipype@0.13.1:
and this is what happens when I try to open it with the CLI utility using Nipype@1.0.4:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
When using CLI utility to open a crash file, if it was generated in a different nipype version, it may show strange/unrelated errors.
Actual behavior
Exceptions from different reasons are shown when a crash file is opened with a different nipype version than the one that generated the crash.
Expected behavior
Better deal with this version difference, at least showing that there is a problem to the user.
How to replicate the behavior
Try to open a crash file from a different nipype version, especially when the classes within the crash were changed.
Script/Workflow details
N/A
Platform details:
Please paste the output of:
python -c "import nipype; print(nipype.get_info()); print(nipype.__version__)"
The text was updated successfully, but these errors were encountered: