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
should handle this case. That is the easy fix to not let it crash.
The harder fix is to figure out why the process_state is None. The only entry point I know for creating a process is when they are run or submitted, but in this case they should be directly in state Created, after that the process state is never set to None AFAIK. If no one has an idea we can first implement the above fix. When the application does not crash, we might get more information.
The process definition allows a None state but the build_call_graph
utils function intended for a creating printable output of the call
graph does crash in this case. A None state indicates some undefined
behavior in the code, but the application should not fail because of the
formatting of the output. This commit makes build_call_graph handle
None states. Partial fix for aiidateam#6585.
The process definition allows a None state but the build_call_graph
utils function intended for a creating printable output of the call
graph does crash in this case. A None state indicates some undefined
behavior in the code, but the application should not fail because of the
formatting of the output. This commit makes build_call_graph handle
None states. Partial fix for aiidateam#6585.
Steps to reproduce
I called
build_call_graph
every three seconds to get the status of a process. This is used to update the GUI in AiiDAlab.At some point (in rare case, randomly), I got this error:
The text was updated successfully, but these errors were encountered: