Skip to content
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

Export a wrapper around purrr map() to workers rather than map() itself #253

Open
DavisVaughan opened this issue Mar 7, 2023 · 0 comments
Labels
0.4.0 bug an unexpected problem or unintended behavior

Comments

@DavisVaughan
Copy link
Collaborator

To avoid cases where we ship map() from purrr 1.0.0 to the workers, but the workers have purrr < 1.0.0, resulting in an error like:

Error in map_("list", .x, .f, ..., .progress = .progress) : 
  could not find function "map_"

Something like:

# rather than this
...furrr_map <- purrr::map

# do this
...furrr_map <- function(...) {
  purrr::map(...)
}

https://stackoverflow.com/questions/75660223/r-furure-map-across-multiple-servers

@DavisVaughan DavisVaughan added bug an unexpected problem or unintended behavior 0.4.0 labels Mar 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.4.0 bug an unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

1 participant