futureverse/future.apply

Issues

• Rare error in next_random_seed()

  #122 opened 2 months ago
  4

• Nested future_lapply function results in an error for using too many cores

  #121 opened 2 months ago
  5

• Test suite failure on 32bit architectures

  #120 opened 9 months ago
  12

• Bug in documentation for future.globals?

  #119 opened a year ago
  2

• Add test validating that future.globals.maxSize is properly set in nested parallelization

  #118 opened a year ago
  0

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

  #117 opened a year ago
  1

• Clear up global options usage with nested plans

  #116 opened a year ago
  4

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

  #114 opened 2 years ago
  3

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

  #112 opened 2 years ago
  2

• Include simple .progress switch in future_lapply

  #111 opened 2 years ago
  2

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

  #110 opened 2 years ago
  3

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

  #109 opened 2 years ago
  1

• BUG: Correlated RNG with nested future.apply calls

  #108 opened 2 years ago
  3

• CLEANUP: getOption() speedup only needed in R (< 4.0.0)

  #107 opened 2 years ago
  0

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

  #106 opened 2 years ago
  1

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

  #105 opened 2 years ago
  4

• CRAN submission: Found the following files/directories: 'Rscript2af8ccbfb3f34' 'Rscript92e8cbfb3f24'

  #104 opened 2 years ago
  1

• Error setallcol(x): verbose must be TRUE or FALSE`

  #103 opened 3 years ago
  2

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

  #102 opened 3 years ago
  2

• When stopping with an error, return the item that caused the error

  #101 opened 3 years ago
  4

• Unexpected behavior of `future.seed = NULL`

  #100 opened 3 years ago
  2

• Overhead when exporting to PSOCK cluster

  #98 opened 3 years ago
  5

• The worker is not freed if the call is interrupted.

  #97 opened 3 years ago
  1

• Add future_pvec() analogue to parallel::pvec()

  #96 opened 3 years ago
  2

• Harmonize order of `...` and `future.*` arguments

  #95 opened 3 years ago
  1

• CLEANUP: Remove argument future.lazy

  #94 opened 3 years ago
  0

• mapply(): Align with recent R-devel updates

  #93 opened 3 years ago
  0

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

  #92 opened 3 years ago
  0

• RStudio disconnected with R

  #89 opened 3 years ago
  6

• Using multiple cores in RStudio

  #88 opened 3 years ago
  7

• future.apply masking data.table subset operations

  #87 opened 4 years ago
  2

• C stack usage error

  #86 opened 3 years ago
  6

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

  #85 opened 3 years ago
  0

• future.apply::future_lapply is not a blocking call in certain situations

  #84 opened 3 years ago
  7

• Adding customChunks to future.apply functions

  #83 opened 4 years ago
  5

• Question regarding googleanalyticsR

  #82 opened 4 years ago
  2

• Odd error with future.apply after loading BiocGenerics

  #81 opened 4 years ago
  3

• two minor questions

  #80 opened 3 years ago
  7

• immediateCondition not immediate for sequential?

  #79 opened 4 years ago
  3

• Struggling to get cluster plan working

  #78 opened 4 years ago
  5

• multisession returns unexpected results when cropping stars

  #77 opened 4 years ago
  2

• is this package by-default run on multicore?

  #76 opened 4 years ago
  2

• making stop() immediate

  #75 opened 4 years ago
  2

• future.apply::future_lapply() processes never complete

  #74 opened 4 years ago
  17

• DOCS: Huh ... the first future.apply example is ... hmm

  #72 opened 4 years ago
  0

• future.lapply CRAN package not available for my version of R (4.0.3)

  #71 opened 4 years ago
  0

• Environment for future_lapply

  #70 opened 4 years ago
  3

• Incorporate R-devel bug fix PR#17969

  #69 opened 4 years ago
  1

• Overhead of future_lapply relative to parLapply/mclapply, etc.

  #68 opened 4 years ago
  4

• multiple future_lapply's inside a function only the first is parallel.

  #67 opened 4 years ago
  9