-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Errors in remote asynchronous tasks lose their error message when displayed on the caller on Julia 1.6 #40337
Labels
error handling
Handling of exceptions by Julia or the user
parallelism
Parallel or distributed computation
regression
Regression in behavior compared to a previous version
Comments
JeffBezanson
added a commit
that referenced
this issue
Apr 7, 2021
JeffBezanson
added a commit
that referenced
this issue
Apr 7, 2021
JeffBezanson
added a commit
that referenced
this issue
Apr 8, 2021
KristofferC
pushed a commit
that referenced
this issue
Apr 11, 2021
ElOceanografo
pushed a commit
to ElOceanografo/julia
that referenced
this issue
May 4, 2021
antoine-levitt
pushed a commit
to antoine-levitt/julia
that referenced
this issue
May 9, 2021
johanmon
pushed a commit
to johanmon/julia
that referenced
this issue
Jul 5, 2021
staticfloat
pushed a commit
that referenced
this issue
Dec 23, 2022
Keno
pushed a commit
that referenced
this issue
Jun 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
error handling
Handling of exceptions by Julia or the user
parallelism
Parallel or distributed computation
regression
Regression in behavior compared to a previous version
Cross-posting from discourse as there was no response there
On Julia 1.6:
The error message is lost here. If we do something similar on a local process,
the error message is displayed correctly. This also works correctly if the remote error is not wrapped in
@async
:This worked correctly on 1.5.4:
Edit: It appears that the error is propagated correctly on Julia 1.6, so this is a display issue?
The text was updated successfully, but these errors were encountered: