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
Hi, I posted on Discourse but no answer so far, so maybe it's better here?
I have trouble getting the error type/message when running PyCall with @distributed (when exceptions are raised in Python). It seems that it's the stack trace which poses problem, but I don't know if it is a known limitation or a bug? From PyCall or from Distributed?
I just tried with julia1.10, PyCall v1.96.4, it seems that even though the stacktrace changed it still raises a ProcessExitedException(2), while without distributing you would get a PyError of class 'ZeroDivisionError'. And it seems to be the same even if using a try/catch inside the spawnat call. I guess that this is not the expected behavior?
Hi, I posted on Discourse but no answer so far, so maybe it's better here?
I have trouble getting the error type/message when running PyCall with
@distributed
(when exceptions are raised in Python). It seems that it's the stack trace which poses problem, but I don't know if it is a known limitation or a bug? From PyCall or from Distributed?The text was updated successfully, but these errors were encountered: