-
Notifications
You must be signed in to change notification settings - Fork 86
Issues: futureverse/future
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
WISH: Add method for interrupting / terminating a future
feature request
feature/terminate
Frontend API
Part of the Future API that users of futures rely on
Suggestion: future::with_plan() and/or future::local_plan()
feature request
#263
opened Nov 12, 2018 by
wlandau
Would be nice to have a "make everyting use future" function
#162
opened Aug 28, 2017 by
DarwinAwardWinner
nested futures that doesn't terminate
cannot-parallelize-bc-non-exportable-object
documentation
#348
opened Nov 7, 2019 by
EmilRehnberg
BACKEND: ClusterMQ as a new backend
Backend API
Part of the Future API that only backend package developers rely on
feature request
#204
opened Mar 10, 2018 by
alexvorobiev
DOCUMENTATION: A vignette / example with a basic Shiny app using futures
documentation
enhancement
help wanted
#140
opened Apr 5, 2017 by
PeterVermont
Error when using envir & globals parameters in futures that are not using the multisession plan
#280
opened Feb 11, 2019 by
avsdev-cw
Cannot find symbols exported to node by parallel::clusterExport
Backend API
Part of the Future API that only backend package developers rely on
feature request
feature/sticky-globals
globals
Only "sequental' plan can work
waiting on
Waiting on a follow-up reply
#649
opened Sep 29, 2022 by
Yunuuuu
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.