futureverse/future.apply issues and pull requests

#122 - Rare error in next_random_seed()

Issue - State: closed - Opened by mb706 4 months ago - 4 comments

#121 - Nested future_lapply function results in an error for using too many cores

Issue - State: closed - Opened by mcoghill 10 months ago - 5 comments
Labels: bug, for-future-pkg

#120 - Test suite failure on 32bit architectures

Issue - State: closed - Opened by tillea almost 1 year ago - 12 comments

#119 - Bug in documentation for future.globals?

Issue - State: closed - Opened by snowpong about 1 year ago - 2 comments

#118 - Add test validating that future.globals.maxSize is properly set in nested parallelization

Issue - State: closed - Opened by HenrikBengtsson about 1 year ago

#117 - future_tapply(): Creation of error on 'INDEX' being a formula only working in R (>= 4.3.0) would fail in R (< 3.6.0)

Issue - State: closed - Opened by HenrikBengtsson about 1 year ago - 1 comment
Labels: bug

#116 - Clear up global options usage with nested plans

Issue - State: closed - Opened by maxim-h over 1 year ago - 4 comments
Labels: bug, feature request

#115 - Fixes #108 Correlated RNG with nested future.apply calls

Pull Request - State: open - Opened by shikokuchuo over 1 year ago - 1 comment

#114 - Error in parallel execution using future_lapply with R6 objects and the get() function Description:

Issue - State: closed - Opened by sohappy1140937786 over 1 year ago - 3 comments

#112 - future_lapply(X, FUN = with, a) looks for 'a' in the wrong environment

Issue - State: open - Opened by HenrikBengtsson over 1 year ago - 2 comments

#111 - Include simple .progress switch in future_lapply

Issue - State: open - Opened by frederikziebell over 1 year ago - 2 comments
Labels: feature request

#110 - future_lapply() & future_mapply() chunk with `[` causing loss of class attributes needed for subsetting with `[[`

Issue - State: closed - Opened by HenrikBengtsson almost 2 years ago - 3 comments

#109 - Align `future_tapply()` with updates to `tapply()` in the up-coming R-4.3.0

Issue - State: closed - Opened by HenrikBengtsson almost 2 years ago - 1 comment

#108 - BUG: Correlated RNG with nested future.apply calls

Issue - State: open - Opened by HenrikBengtsson almost 2 years ago - 3 comments
Labels: bug

#107 - CLEANUP: getOption() speedup only needed in R (< 4.0.0)

Issue - State: closed - Opened by HenrikBengtsson about 2 years ago

#106 - future_by() should not accept specifying FUN as a character, because by() doesn't

Issue - State: closed - Opened by HenrikBengtsson over 2 years ago - 1 comment

#105 - future_sapply() does not support FUN specified as a character string, e.g. FUN = "[["

Issue - State: closed - Opened by jpjoines over 2 years ago - 4 comments
Labels: bug

#104 - CRAN submission: Found the following files/directories: 'Rscript2af8ccbfb3f34' 'Rscript92e8cbfb3f24'

Issue - State: closed - Opened by HenrikBengtsson over 2 years ago - 1 comment

#103 - Error setallcol(x): verbose must be TRUE or FALSE`

Issue - State: closed - Opened by tle4336 over 2 years ago - 2 comments

#102 - Error on modifying by reference with `data.table::set()` in the context of `future.apply::future_apply()` or `furrr::future_map()`

Issue - State: closed - Opened by ramiromagno almost 3 years ago - 2 comments

#101 - When stopping with an error, return the item that caused the error

Issue - State: open - Opened by Kodiologist almost 3 years ago - 4 comments
Labels: feature request

#100 - Unexpected behavior of `future.seed = NULL`

Issue - State: closed - Opened by odelmarcelle almost 3 years ago - 2 comments

#99 - Strip environment from exported function

Pull Request - State: closed - Opened by odelmarcelle almost 3 years ago - 2 comments

#98 - Overhead when exporting to PSOCK cluster

Issue - State: open - Opened by odelmarcelle almost 3 years ago - 5 comments

#97 - The worker is not freed if the call is interrupted.

Issue - State: open - Opened by randy3k about 3 years ago - 1 comment

#96 - Add future_pvec() analogue to parallel::pvec()

Issue - State: open - Opened by HenrikBengtsson about 3 years ago - 2 comments

#95 - Harmonize order of `...` and `future.*` arguments

Issue - State: closed - Opened by HenrikBengtsson over 3 years ago - 1 comment

#94 - CLEANUP: Remove argument future.lazy

Issue - State: closed - Opened by HenrikBengtsson over 3 years ago

#93 - mapply(): Align with recent R-devel updates

Issue - State: closed - Opened by HenrikBengtsson over 3 years ago

#92 - Calling `.traceback()` within `future_Map` function call can slow things down terribly depending on data size

Issue - State: open - Opened by arunsrinivasan over 3 years ago

#90 - SECIURITY

Pull Request - State: closed - Opened by MINATILO over 3 years ago - 2 comments

#89 - RStudio disconnected with R

Issue - State: closed - Opened by waynelapierre over 3 years ago - 6 comments
Labels: invalid

#88 - Using multiple cores in RStudio

Issue - State: closed - Opened by waynelapierre over 3 years ago - 7 comments
Labels: question

#87 - future.apply masking data.table subset operations

Issue - State: closed - Opened by grantmcdermott over 3 years ago - 2 comments

#86 - C stack usage error

Issue - State: closed - Opened by waynelapierre over 3 years ago - 6 comments

#85 - TESTS: Add test for future_lapply(1, FUN = function(x) a, future.globals = list(a = 42))

Issue - State: closed - Opened by HenrikBengtsson over 3 years ago
Labels: pkg-test-needed

#84 - future.apply::future_lapply is not a blocking call in certain situations

Issue - State: closed - Opened by vsrdharca over 3 years ago - 7 comments
Labels: question

#83 - Adding customChunks to future.apply functions

Issue - State: open - Opened by bgall almost 4 years ago - 5 comments
Labels: feature request

#82 - Question regarding googleanalyticsR

Issue - State: closed - Opened by XoliloX almost 4 years ago - 2 comments

#81 - Odd error with future.apply after loading BiocGenerics

Issue - State: closed - Opened by DarwinAwardWinner almost 4 years ago - 3 comments
Labels: bug

#80 - two minor questions

Issue - State: closed - Opened by waynelapierre almost 4 years ago - 7 comments
Labels: question

#79 - immediateCondition not immediate for sequential?

Issue - State: closed - Opened by rickhelmus about 4 years ago - 3 comments

#78 - Struggling to get cluster plan working

Issue - State: closed - Opened by tylerlittlefield about 4 years ago - 5 comments

#77 - multisession returns unexpected results when cropping stars

Issue - State: closed - Opened by johnbaums about 4 years ago - 2 comments
Labels: question, globals

#76 - is this package by-default run on multicore?

Issue - State: closed - Opened by ravinder387 about 4 years ago - 2 comments
Labels: question

#75 - making stop() immediate

Issue - State: open - Opened by rickhelmus about 4 years ago - 2 comments
Labels: feature request

#74 - future.apply::future_lapply() processes never complete

Issue - State: closed - Opened by adamhsparks about 4 years ago - 17 comments

#73 - Linkify mention of future_lapply()

Pull Request - State: closed - Opened by Bisaloo about 4 years ago - 2 comments

#72 - DOCS: Huh ... the first future.apply example is ... hmm

Issue - State: closed - Opened by HenrikBengtsson about 4 years ago
Labels: documentation

#71 - future.lapply CRAN package not available for my version of R (4.0.3)

Issue - State: closed - Opened by thevictorian about 4 years ago

#70 - Environment for future_lapply

Issue - State: open - Opened by dipterix about 4 years ago - 3 comments
Labels: globals

#69 - Incorporate R-devel bug fix PR#17969

Issue - State: closed - Opened by HenrikBengtsson about 4 years ago - 1 comment

#68 - Overhead of future_lapply relative to parLapply/mclapply, etc.

Issue - State: open - Opened by traversc about 4 years ago - 4 comments

#67 - multiple future_lapply's inside a function only the first is parallel.

Issue - State: closed - Opened by Dekermanjian over 4 years ago - 9 comments
Labels: question

#66 - R-devel: sprintf() coding mistakes

Issue - State: closed - Opened by HenrikBengtsson over 4 years ago
Labels: bug

#65 - using future_apply inside a future

Issue - State: open - Opened by comicfans over 4 years ago

#64 - Missing globals in `future_lapply`

Issue - State: open - Opened by conroylau over 4 years ago - 2 comments
Labels: question, for-globals-pkg, globals

#63 - lapply, passing through any intermediate remotes

Issue - State: open - Opened by myoung3 over 4 years ago

#62 - Where should character globals be looked up?

Issue - State: open - Opened by DavisVaughan over 4 years ago
Labels: globals

#61 - multisession does not work with dots but multicore does

Issue - State: closed - Opened by tdhock over 4 years ago - 6 comments

#60 - finer control over future_lapply()

Issue - State: open - Opened by MLopez-Ibanez over 4 years ago - 1 comment
Labels: feature request

#59 - Export make_rng_seeds()?

Issue - State: open - Opened by mllg over 4 years ago - 2 comments
Labels: RNG

#58 - future_apply(): Add argument simply = TRUE

Issue - State: closed - Opened by HenrikBengtsson over 4 years ago
Labels: enhancement

#57 - ROBUSTNESS: Add explicit 'stringsAsFactors' arguments [data.frame]

Issue - State: closed - Opened by HenrikBengtsson almost 5 years ago - 1 comment

#56 - Replace 'multiprocess' with 'multisession' in examples and other docs

Issue - State: closed - Opened by HenrikBengtsson almost 5 years ago

#55 - future.seed error with future_apply

Issue - State: closed - Opened by eweisbrod almost 5 years ago - 5 comments
Labels: bug

#54 - Implement future version of .mapply() ?

Issue - State: closed - Opened by mllg almost 5 years ago - 5 comments
Labels: feature request, pkg-test-needed

#53 - future_lapply() aware of objects not listed in future.globals

Issue - State: closed - Opened by eszterb99 almost 5 years ago - 3 comments
Labels: question

#52 - Feature request: purrr-like sugar functions

Issue - State: closed - Opened by pat-s almost 5 years ago - 6 comments
Labels: feature request

#51 - future_mapply tries to subset MoreArgs if future.seed = TRUE

Issue - State: closed - Opened by mllg almost 5 years ago - 3 comments
Labels: bug

#48 - How can I do 'multiprocess' on remote clusters without nested future_*apply?

Issue - State: closed - Opened by seonghobae about 5 years ago - 2 comments
Labels: question

#47 - Not exporting variable that is assigned again in apply function

Issue - State: closed - Opened by renkun-ken over 5 years ago - 7 comments
Labels: bug

#44 - Non-blocking, local evaluation of future_lapply()?

Issue - State: open - Opened by danschrage over 5 years ago - 8 comments
Labels: feature request

#43 - attr(future.scheduling, "ordering") does not relay output in the proper order

Issue - State: closed - Opened by HenrikBengtsson over 5 years ago - 1 comment
Labels: documentation

#42 - Possible bug in loading packages

Issue - State: open - Opened by arunsrinivasan almost 6 years ago - 2 comments
Labels: feature request, for-future-pkg

#40 - future.debug = TRUE: Error in sprintf(...) : 'fmt' length exceeds maximal format length 8192

Issue - State: closed - Opened by andrewrech almost 6 years ago - 5 comments
Labels: bug

#39 - Performance of future_apply vs apply

Issue - State: closed - Opened by Nowosad almost 6 years ago - 7 comments
Labels: enhancement, for-future-pkg

#38 - How to allow printing to the console inside a future?

Issue - State: closed - Opened by xiaodaigh almost 6 years ago - 3 comments
Labels: question

#37 - Question: best way to prioritise cluster local vars if they exist

Issue - State: closed - Opened by arunsrinivasan about 6 years ago - 6 comments
Labels: bug

#36 - Fetching globals assigned as function arguments fails when run in parallel

Issue - State: open - Opened by arunsrinivasan about 6 years ago - 6 comments
Labels: for-future-pkg, globals

#35 - request/wish: future_by() function

Issue - State: closed - Opened by ddisab01 about 6 years ago - 6 comments
Labels: feature request

#34 - progress bar

Issue - State: closed - Opened by talegari about 6 years ago - 6 comments

#33 - Add callbacks

Issue - State: closed - Opened by dipterix about 6 years ago - 4 comments
Labels: for-future-pkg

#32 - Graceful error handling in future_lapply

Issue - State: open - Opened by jburos over 7 years ago - 6 comments
Labels: feature request

#31 - Workflow for reproducing future_lapply results

Issue - State: closed - Opened by matherealize about 6 years ago - 3 comments
Labels: documentation, RNG

#30 - Expose evaluator argument of future?

Issue - State: closed - Opened by kendonB over 6 years ago - 8 comments
Labels: feature request

#29 - Problem with multicore on macOS

Issue - State: closed - Opened by magic-lantern over 6 years ago - 13 comments

#28 - A list of data.table - result of future_lapply - lost side effect (reference semantic)

Issue - State: closed - Opened by ThoDuyNguyen over 6 years ago - 7 comments

#27 - Single future.control argument rather than multiple, individual future.* arguments

Issue - State: open - Opened by HenrikBengtsson over 6 years ago - 9 comments
Labels: feature request

#26 - Add arguments future.stdout (and future.stderr)

Issue - State: closed - Opened by HenrikBengtsson over 6 years ago - 15 comments
Labels: enhancement

#25 - Add option to randomize order of execution

Issue - State: closed - Opened by mllg over 6 years ago - 11 comments
Labels: feature request

#23 - future.apply not working with fst package

Issue - State: closed - Opened by matthiasgomolka over 6 years ago - 4 comments

#20 - SPEED: Add support for per-chunk/per-future seeds

Issue - State: open - Opened by HenrikBengtsson over 6 years ago
Labels: RNG

#18 - Locally defined S3 methods are not automatically exported (was: function.type are not loaded as global variables)

Issue - State: closed - Opened by Rloveeee over 6 years ago - 2 comments

#17 - future_mapply throws "Error in seq.int(0, to0 - from, by) : 'to' must be a finite number"

Issue - State: closed - Opened by ThoDuyNguyen over 6 years ago - 4 comments
Labels: bug

#15 - IDEA: Add argument 'future.label' for producing future labels

Issue - State: closed - Opened by HenrikBengtsson over 6 years ago
Labels: help wanted, feature request

#10 - future.globals does not seem to work when variables are "created" in the named list

Issue - State: closed - Opened by DavisVaughan almost 7 years ago - 5 comments
Labels: bug, for-future-pkg, globals

#7 - 'chunk.size' argument

Issue - State: closed - Opened by HenrikBengtsson almost 7 years ago - 1 comment
Labels: feature request

#2 - Distribute different tasks to different types of compute resources

Issue - State: open - Opened by wlandau-lilly about 7 years ago - 1 comment

#1 - What is future.lapply(..., future.lazy = TRUE) supposed to do?

Issue - State: closed - Opened by HenrikBengtsson about 7 years ago - 12 comments
Labels: question

GitHub / futureverse/future.apply issues and pull requests