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
Exceptions raised in qcop, e.g., sending a "transition_state" calculation to "psi4" which doesn't support it will result in 500 errors because I don't generically handle exceptions on this endpoint.
The issue is that in qcop I choose to raise certain exceptions upfront before the program is ever called and do not create exc.program_failure objects for them. So these exceptions get raised in ChemCloud and I do not have the associated .input_data to create a proper ProgramFailure objects.
I think the best fix will be to handle ALL exceptions in qcop the same way and append a .program_failure object to them.
The text was updated successfully, but these errors were encountered:
Exceptions raised in
qcop
, e.g., sending a "transition_state" calculation to "psi4" which doesn't support it will result in 500 errors because I don't generically handle exceptions on this endpoint.The issue is that in
qcop
I choose to raise certain exceptions upfront before theprogram
is ever called and do not createexc.program_failure
objects for them. So these exceptions get raised in ChemCloud and I do not have the associated.input_data
to create a properProgramFailure
objects.I think the best fix will be to handle ALL exceptions in
qcop
the same way and append a.program_failure
object to them.The text was updated successfully, but these errors were encountered: