Closed HenrikBengtsson closed 4 years ago
Thanks for the report and suggesting the solution.
Thanks. I've verified that kernelboot (master branch) works with the upcoming future 1.15.0, which I'd like to submit to CRAN rather soon. Would you mind submitting your kernelboot 0.1.6 to CRAN as soon as you have time?
@HenrikBengtsson I submitted it a week ago but they still didn't upload it...
Your package is sitting in ftp://cran.r-project.org/incoming/waiting/, which means CRAN is waiting for a response from you. Could be a hickup while running your tests triggering a false NOTE, WARNING, or ERROR. Check you emails / spam folder - what was the latest email notification you've got from them on Oct 31/Nov 1?
Correction: CRAN is waiting for a response from you
@HenrikBengtsson I wrote them two times. Unfortunately there is some strange warning in their autochecks, that does not seem to be related to my package. There doesn't seem much that I can do about it. Again, thanks for noticing me about the bug.
I see; I guess they just have a big backlog. Hopefully, this hurdle is just a one-time hiccup and it'll be smoother next time. Thxs.
I see kernelboot 0.1.6 is on CRAN now. Thxs again
Hi, your
kernelboot::kernelboot()
assumes that.Random.seed
exists (see below) but that is not always guaranteed to be the case.I think the simplest solution is to use:
The reason why you haven't run into problems with this yet is when loading future (<= 1.14.0) together with your package, a side-effect was that
.Random.seed
was (incorrectly) created. I've now cleaned this up, which means that with future (> 1.14.0).Random.seed
may not be set. When running reverse package dependency checks,R CMD check kernelboot_0.1.5.tar.gz
now produces: