Closed HenrikBengtsson closed 5 years ago
This RStudio issue has some more info on why forking can be problematic in its R session wrapper: https://github.com/rstudio/rstudio/issues/2597
I'll go with this warning for the next release.
Same issue here version 1.15.0
@kaizen89, I'm not sure what "same issue" means. Note that the warning (https://github.com/HenrikBengtsson/future/issues/318#issue-456472836) is intentional and serves to inform RStudio users. We want that warning - without the warning people were more confused.
Oups, sorry. I read the post too fast. So this means that we can no longer use multicore processing with future?
Please read the warning: "... For more details, how to control forked processing or not, and how to silence this warning in future R sessions, see ?future::supportsMulticore ?parallelly::supportsMulticore"
Several RStudio users were caught by surprise when they updated to future 1.13.0 and (after troubleshooting) discovered that forked processing is now disabled when running R from the RStudio environment. Sorry about that. I can imagine that more people are still discovering this change in behavior, or find it odd, or it doesn't match up with examples they find online, in vignettes etc.
Because of this, I just added the below warning to the development branch (to become future 1.14.0). Is this a good idea, or will that introduce additional confusion?