Hi Ben, reading the comments from https://github.com/ewels/MultiQC/issues/376 it seems that in the upcoming release they will solve the problem. Are we going to wait for the next v. 1.0 or include it now and update later ?
-- Ra On Mon, Dec 26, 2016 at 1:18 PM Ben Woodcroft <b.woodcr...@uq.edu.au> wrote: > Hi Raoul, > > > On 26/12/16 20:45, Ra wrote: > > Hi Ben, > > thanks I will investigate. Does it mean that multiqc is in stand by > > for now ? > > It would be ideal I think to add tests, and because they are failing it > would be good to know why. I thought the easiest simply to ask the > maintainers if they knew why the tests were failing: > https://github.com/ewels/MultiQC/issues/376 > > I also submitted the exception catching patch here, which we should add > to our patch if we decide to keep it before pushing our changes. > https://github.com/ewels/MultiQC/pull/377 > > I figure it makes sense to give them a week or two to respond, and > reevaluate after that. I presume you have not observed any problems > using multiqc after this update? > Thanks, > ben >
