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
Capture and relay call frames on errors #478
Milestone
Comments
Maybe the first is to just record the above info in the future result |
|
HenrikBengtsson
changed the title
future: record recover() info on errors
Capture and relay call frames on errors
Mar 25, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Idea
The idea is to have the future record the full recover stack in the FutureResult object. Something like the info in:
and then regenerate this call stack when relaying the error on the parent R process. I'm not sure if/not the latter can be done, but if we can figure it out, it'll be super cool.
It might be expensive to transfer all call stacks back from the worker to the main R session when running in parallel, so maybe this needs to be enabled via an option, e.g.
options(future.recover.enable = TRUE)
. It might be that we can enable it by default forsequential
futures.See also
#253
The text was updated successfully, but these errors were encountered: