danschrage

> By design it mimics lapply() as far as ever possible, including blocking. > See also the Roadmap section in the package vignette or the README here on GitHub. Thanks...

I guess this is ultimately a feature request, since it's not the intended behavior of `future_lapply()`. I'll leave this issue open, but if you don't think it makes sense to...

I have this same issue, more or less (though I have an RM1). I was on 2.7.0.51 and wanted to downgrade to 2.5.1.47. In my case, the downgrade was successful....

I tried deleting the public keys (there was a third copy in / for me) and setting to version 1.0.0.0. But it still grabbed the 2.8.0.86 version and went ahead...

I solved my problem the old-fashioned way: by wiping everything and starting fresh. I used ddvk's uuuflash tool (https://github.com/ddvk/remarkable-uuuflash) to wipe the device and put 2.1.1.3 back on both partitions....

Note that this stems from the same underlying cause as this issue in the `prediction` package (on which `margins` depends): https://github.com/leeper/prediction/issues/35 The issue is that `margins` often selects variables from...

Any open-source license is fine with me. On Wed, Jul 12, 2017 at 1:34 PM, Ulrich Gabor wrote: > You can put any license you want on my contribution. >...