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

Parallel clusters don't respect environment manipulations (in particular libpaths) #377

Closed
gowerc opened this issue Oct 26, 2022 · 0 comments · Fixed by #435
Closed

Parallel clusters don't respect environment manipulations (in particular libpaths) #377

gowerc opened this issue Oct 26, 2022 · 0 comments · Fixed by #435
Labels
bug Something isn't working
Milestone

Comments

@gowerc
Copy link
Collaborator

gowerc commented Oct 26, 2022

When creating parallel clusters the users current environment is not taken into consideration. I.e. if the user manually changed their lib paths this would not be reflected in the parallel process.

This is kind of an anti-pattern as if the users are configuring their libpaths this should be done globally via the .Rprofile file so question (1) would be do we want to provide a solution for this?

If yes; 1 option could be that the ncores argument could take a cluster object which gives the user an entrypoint to manually configure the path (or other oddities of their project) prior to handing us the cluster.

Another option could be we just extend a "lib" argument for setting lib paths in the clusters (assuming that is the only oddity that they might want to configure).

@gowerc gowerc added the bug Something isn't working label Oct 26, 2022
@gowerc gowerc added this to the v1.3.0 milestone Oct 3, 2024
@gowerc gowerc linked a pull request Oct 4, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant