Ben Topping

Getting the same issue as well. Been using this package for a while with no issues but pulled it again for the first time in a while and it's broken...

Hi @olbat thanks for having a look into this! I've just tested the latest image on an Ubuntu instance (18.04.5 LTS) Unfortunately it looks like the cups docker image is...

I recently had a bit of free time and did a bit of digging into the issue. When accessing a page that would return 404 I was getting this error...

**Work breakdown** 1. **(size: S)** I can create batches of 2 for NovaSeqX - [We can change the pipeline min_size in the record loader](https://github.com/sanger/sequencescape/blob/develop/config/default_records/pipelines/default_records.yml#L38) and manually change this value in...

@dasunpubudumal Good question. I think limiting to the custom validator is the most flexible option. It may cause some code duplication but it allows greater flexibility. It might also be...

@dasunpubudumal The idea for this story it to setup the sequencing pipelines in such a way that allows us to use custom validators for NovaSeqX PE and Novaseq 6000 PE...

> > Couple comments but overall on the right track. > > Just to clarify - this implementation has a base BatchValidator for all pipelines and if you want to...

@KatyTaylor I'm not sure whether its worth fixing the historical data. I don't think we will be able to determine when the requests were originally started and hence when the...

Closing as confirmed with Anna G there is no need to back fill historical data for billing and there is no advantage for us except occasionally we will need to...

@neilsycamore The tests suggest that it should be allowed but whether that is correct or not I do not know.