You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug reports on nipype workflows are becoming essentially useless, as the exceptions now wrap around the original exceptions and we get very little traceback information. Further, the crashfiles that are emitted merely show the same exception and no terminal output that would help diagnose.
A good example of this is nipreps/smriprep#286, where we had to provide users with explicit debugging steps. Below I paste a successful _report/report.rst, which also shows nothing. This is a significant regression.
Summary
Bug reports on nipype workflows are becoming essentially useless, as the exceptions now wrap around the original exceptions and we get very little traceback information. Further, the crashfiles that are emitted merely show the same exception and no terminal output that would help diagnose.
A good example of this is nipreps/smriprep#286, where we had to provide users with explicit debugging steps. Below I paste a successful
_report/report.rst
, which also shows nothing. This is a significant regression.This is recent nipype (>=1.7, I think).
The text was updated successfully, but these errors were encountered: