> I can confirm this. Would it then be appropriate for scMerge to add a
> (>= 1.7.3) after its Imports: entry for SingleCellExperiment?
I don't think this is really necessary; 1.7.3 will propagate soon
enough, at which point people just need to stay updated.
> Basically, before we commit
This is a really important point.
Finding and updating serialized S4 instances that are lying around
as they evolve can be painful and very time-consuming.
We should definitely avoid storing serialized S4 objects on the Hub.
I don't know about ExperimentHub but at least for AnnotationHub I
On Thu, Aug 1, 2019 at 10:36 PM Aaron Lun <
infinite.monkeys.with.keyboa...@gmail.com> wrote:
> One possibility is that this is due to a regression in
> SingleCellExperiment, caused by the altexp updates and other
> refactoring. This should be fixed in 1.7.3, you can check this for
> yourself by
One possibility is that this is due to a regression in
SingleCellExperiment, caused by the altexp updates and other
refactoring. This should be fixed in 1.7.3, you can check this for
yourself by installing drisso/SingleCellExperiment off GitHub.
The other moral of the story is to not use
Hi all,
I am getting a strange build error message for scMerge
(http://bioconductor.org/checkResults/devel/bioc-LATEST/scMerge/malbec1-buildsrc.html)
that reads
+ "C stack usage is too close to the limit” on Linux and Mac and
+ "evaluation nested too deeply: infinite recursion” on Windows,
