Hmm. Very important piece of software so we should try to remedy this. I had assigned some GEOquery problems in the edX class and there were some people who could not get getGEO to work, but the problem seemed intermittent. There was a workaround posted on the support site which involved separate steps for assay and platform data acquisition; ultimately the solution data object was just made available directly.
Can/should we make the build/distribution process robust to data server flakiness? The user may encounter intermittent problems, but the software should still be available IMHO. Reduce server-dependent tests and examples? On Sun, May 8, 2016 at 11:08 AM, Dan Tenenbaum <dtene...@fredhutch.org> wrote: > It has not built since the devel (3.4) builds started. Apparently GEO has > been pretty flaky. > Dan > > > ----- Original Message ----- > > From: "Kasper Daniel Hansen" <kasperdanielhan...@gmail.com> > > To: "bioc-devel" <bioc-devel@r-project.org> > > Sent: Sunday, May 8, 2016 5:54:59 AM > > Subject: [Bioc-devel] GEOquery for Bioc devel > > > I don't see GEOquery for Bioc devel. Is that a mistake somehow? > > > > [[alternative HTML version deleted]] > > > > _______________________________________________ > > Bioc-devel@r-project.org mailing list > > https://stat.ethz.ch/mailman/listinfo/bioc-devel > > _______________________________________________ > Bioc-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/bioc-devel > [[alternative HTML version deleted]] _______________________________________________ Bioc-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
