Closed wlandau closed 1 year ago
Thanks for flagging this! I ran into a similar issues a couple of days ago.
I'm hoping I can fix this as a side-effect of the (almost complete) 0.9.0
release in the next couple of days.
Fixed in https://github.com/mschubert/clustermq/commit/80e8f50d5673f1505b819d90da34e5687d2fd8fa and backported to CRAN on release 0.8.95.4
Issue
With
clustermq
0.8.95.3
andpurrr
1.0.0, I ran into a segfault.Downgrading to
purrr
0.3.5
fixed it, but I do not think it is a bug inpurrr
.Cause
Running this:
I entered a debugger to to get to here:
https://github.com/mschubert/clustermq/blob/68c03c85caa888b0b3d573f5332cb9bb7dde5665/R/work_chunk.r#L58
purrr_lookup[[rettype]]
looks like this:whereas the actual
purrr::pmap
installed on my system looks like this:I suspect the
clustermq
CRAN binary ships with the copied body of eachpurrr
function frompurr_lookup
, and if the installed version ofpurrr
disagrees, then things break.Proposal
I suggest replacing this:
https://github.com/mschubert/clustermq/blob/91b35873ac8603b6d3024be3887b0fb04d8cf09b/R/util.r#L89-L99
with this:
and then instead of this:
https://github.com/mschubert/clustermq/blob/68c03c85caa888b0b3d573f5332cb9bb7dde5665/R/work_chunk.r#L58
maybe this:
I am having trouble installing
clustermq
from the source on my toolchain, but I could submit a PR anyway if you would like.