Closed HenrikBengtsson closed 2 years ago
Created PR https://github.com/hadley/plyr/pull/301 to fix this in plyr.
Good news. This will be supported in the next release of plyr. Due to not having tested this in a while, I had to make a small patch in progressr, but as soon as updated versions of both these packages have been released, this will work.
UPDATE:
Unfortunately, the plyr package ignores the
.progress
argument whenever.parallel = TRUE
. It does this by forcing.progress = "none"
, e.g. inplyr::llply()
there is:This is probably based on the assumption that progress updates do not work in parallel processing. However, that does indeed work when using future + progressr. Here's an example of this when we hack plyr to still use
.progress = "progressr"
internally:which outputs:
and when done: