Skip to content

Issues: futureverse/future.apply

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.

Sign up for GitHub

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

27 Open 83 Closed
27 Open 83 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

future_lapply(X, FUN = with, a) looks for 'a' in the wrong environment
#112 opened May 19, 2023 by HenrikBengtsson
2
Include simple .progress switch in future_lapply feature request
#111 opened May 19, 2023 by frederikziebell
2
BUG: Correlated RNG with nested future.apply calls bug
#108 opened Mar 8, 2023 by HenrikBengtsson Future release (not next)
3
When stopping with an error, return the item that caused the error feature request
#101 opened Apr 13, 2022 by Kodiologist
4
Overhead when exporting to PSOCK cluster
#98 opened Mar 10, 2022 by odelmarcelle
5
The worker is not freed if the call is interrupted.
#97 opened Dec 6, 2021 by randy3k Future release (not next)
1
Add future_pvec() analogue to parallel::pvec()
#96 opened Nov 23, 2021 by HenrikBengtsson
2
Calling .traceback() within future_Map function call can slow things down terribly depending on data size
#92 opened Aug 27, 2021 by arunsrinivasan
Adding customChunks to future.apply functions feature request
#83 opened May 6, 2021 by bgall
5
making stop() immediate feature request
#75 opened Dec 20, 2020 by rickhelmus Future release (not next)
2
Environment for future_lapply globals
#70 opened Nov 28, 2020 by dipterix Future release (not next)
3
Overhead of future_lapply relative to parLapply/mclapply, etc.
#68 opened Nov 13, 2020 by traversc
4
using future_apply inside a future
#65 opened Sep 11, 2020 by comicfans
Missing globals in future_lapply for-globals-pkg globals question
#64 opened Sep 1, 2020 by conroylau
2
lapply, passing through any intermediate remotes
#63 opened Aug 4, 2020 by myoung3
Where should character globals be looked up? globals
#62 opened Jul 29, 2020 by DavisVaughan Future release (not next)
finer control over future_lapply() feature request
#60 opened Jun 24, 2020 by MLopez-Ibanez
3 tasks
1
Export make_rng_seeds()? RNG
#59 opened Jun 18, 2020 by mllg
2
Non-blocking, local evaluation of future_lapply()? feature request
#44 opened May 24, 2019 by danschrage
8
Possible bug in loading packages feature request for-future-pkg
#42 opened Apr 18, 2019 by arunsrinivasan Future release (not next)
2
Fetching globals assigned as function arguments fails when run in parallel for-future-pkg globals
#36 opened Feb 5, 2019 by arunsrinivasan
6
Single future.control argument rather than multiple, individual future.* arguments feature request
#27 opened Sep 13, 2018 by HenrikBengtsson
9
SPEED: Add support for per-chunk/per-future seeds RNG
#20 opened Aug 7, 2018 by HenrikBengtsson Future release (not next)
PERFORMANCE: Search large X:s for globals is slow [SOLVED] enhancement
#13 opened Jun 21, 2018 by HenrikBengtsson
3
collaborate with furrr? (purrr futures)
#9 opened Apr 15, 2018 by r2evans
ProTip! Type g i on any issue or pull request to go back to the issue listing page.