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

parallelExport() doesn't work properly without explicit parallelStart() #17

Closed
larskotthoff opened this issue May 8, 2014 · 1 comment

Comments

@larskotthoff
Copy link
Member

In my configuration, I have parallelMap.default.autostart = TRUE. This does not work properly in conjunction with parallelExport() -- I'm getting messages about the specified objects being exported and imported again, but subsequent code fails saying that those objects are undefined.

If I add an explicit parallelStart() before doing the exports, everything works fine.

@berndbischl
Copy link
Member

Thx for the report and sorry for taking so long.

I have decided to remove the autostart option.
It was not really possible to have stable and bug free package with this, when I offer nice things as parallelLibrary, parallelExport and so on.
(there are simply too many places where you must potentially "autostart")

I have decided that the user does not lose so much when I remove this option, and he has to write 1 line more, but gains a lot in stability and usability.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants