Closed HenrikBengtsson closed 4 years ago
Thanks for the FYI
I noticed that you also submitted new versions of your packages around the same time I did submit sctransform v0.3. Don't understand how the reverse dependency checks would link the Seurat errors to the wrong package - don't they test each package one-by-one?
In any case, Seurat developers and I are aware of the breaking changes and a fix is underway.
I re-submitted again yesterday, because there was another, real revdep error. In the new submission, they got these new errors, probably because sctransform 0.3.0 is rolling out right now. It's probably because the old version of future (1.18.0) was tested with sctransform 0.2.1 and the new future (1.19.1) with sctransfrom 0.3.0.
BTW, if you're not running https://github.com/r-lib/revdepcheck, it's pretty useful and quite straightforward.
Feel free to close or leave it open for others who might wonder.
Seems to be fixed in Seurat 3.2.2
Hi, just want to let you know that the CRAN checks on Seurat started to fail when sctransform 0.3.0 reached CRAN; at least there's a strong correlation with the new and the old version number. The errors appear to be due to, numerically reproducible, but different numeric results:
PS. I noticed this because CRAN's reverse-dependency checks on my future packages incorrectly linked it to my update.
cc/ @satijalab