Simon Sadedin

Should be merged in now. On Mar 20, 2017 8:05 PM, "marchoeppner" wrote: > Hi, > anything else that needs testing here? Or will this be merged into master >...

It sounds like we definitely want to support that. I think it needs to be optional, there has been some [discussion about it before](https://github.com/ssadedin/bpipe/issues/156#issuecomment-133046147). I'll look at adding this option.

thanks @slagelwa - I will see if there is any reason these dependencies were pinned and what we need to do to update them.

@slagelwa - any chance you could share the actual command line / configuration you are running with trivy? Will be helpful to check the problem is resolved.

hi @akhileshmishra0908 .... just checking the pipeline code, it looks to me like the problem you're hitting may have been addressed in [this commit](https://github.com/Oshlack/Clinker/commit/503256a40c7fd82654a6db1e4ef16f4f7d313c97). I'm thinking it may be a...

Closing due to inactivity

Wow, that is way more than I would have expected. The polling frequency is supposed to be controlled by some parameters and to use an exponential backoff (so, fast at...

Wow, it definitely should not be querying that often. If the pipeline has very high concurrency and a lot of short jobs then perhaps I could imagine it - but...

Thanks for all the discussion on this. I'm considering two separate actions to try and alleviate this problem: * consolidated job polling (see #213) * detection of command exit based...

I did some quick investigation and it looks like this error is likely to be thrown if you are using CRAM files and the reference you supply has contigs that...