-
Notifications
You must be signed in to change notification settings - Fork 84
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
Globals specified as a named list not exported with map-reduce APIs for certain backends #515
Comments
I think a reproducible example based on plain sequential futures is: library(future)
plan(sequential)
f <- future(fcn(), globals = list(a=42, fcn=function() a))
value(f)
## Error in fcn() : object 'a' not found The same works with, say, |
This fails also with |
Indeed, this is the same problem as in futureverse/future.apply#10 from May 2018. |
HenrikBengtsson
added a commit
that referenced
this issue
Jul 28, 2021
HenrikBengtsson
added a commit
that referenced
this issue
Jul 29, 2021
HenrikBengtsson
added a commit
that referenced
this issue
Aug 6, 2021
HenrikBengtsson
added a commit
that referenced
this issue
May 6, 2022
HenrikBengtsson
added a commit
to HenrikBengtsson/globals
that referenced
this issue
May 6, 2022
HenrikBengtsson
added a commit
that referenced
this issue
May 8, 2022
The bug fix in future 1.22.0 that addressed the issue where object 'a' in future(fcn(), globals=list(a=42, fcn=function() a)) would not be found has been redesigned in a more robust way.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue
and
The above works with other types of backends, e.g.
plan(cluster, workers = 1L)
.Troubleshooting
It works with plain futures:
Since it affects both future.apply and furrr, my best guess is that this needs to be fixed in the future package.
The text was updated successfully, but these errors were encountered: