Johan Dahlberg
04/29/2025, 8:56 AMJames Fellows Yates
04/29/2025, 9:37 AMJames Fellows Yates
04/29/2025, 9:37 AMJohan Dahlberg
04/29/2025, 1:35 PMJames Fellows Yates
04/29/2025, 8:06 PMconda. I was going to say if it was just for a specific 'end point' tool maybe can just block conda support for that module, but I can see why this is quite catastrophic.
So from my PoV this would be fine. I guess the question is more how the removal of support should be implemented. If you expect the conda issue to be resolved in the near future you don't want to do something too drastic. Maybe use the internal nextflow conda.enabled variable to add a check that if it's true throw an error?
What do you think <!subteam^S016E36N7TQ> <!subteam^S044DU0NG68>?Phil Ewels
04/29/2025, 8:17 PMJohan Dahlberg
04/30/2025, 6:47 AMconda.enabled variable and throwing an error if that is true sounds like a good work around for now.
@Phil Ewels we have taken up setting up and maintaining conda packages for other of our dependencies previously, but as you say, this one is just to big and complicated for us to take on.
When you say the docker files should be available along side the module, where does that mean we should place them?
We keep our public containers here: https://github.com/PixelgenTechnologies/pixelator/pkgs/container/pixelator and the docker files and docker-bake file are in the pixelator repo: https://github.com/PixelgenTechnologies/pixelator/tree/devJohan Dahlberg
04/30/2025, 6:47 AMPhil Ewels
04/30/2025, 6:49 AMpixelator CLI specifically, then I think that's fine. If the docker image is for a step in the pipeline which is pipeline-specific (eg. includes multiple tools etc), then the module-specific Dockerfile should be kept in the module directory basically. And the image pushed to quay.io/nf-corePhil Ewels
04/30/2025, 6:49 AMJohan Dahlberg
04/30/2025, 6:56 AMpixelator tool. I think for us the easiest way to do this would be to keep the containers on github. I think from the community point of view, since we have everything under and open-source license it should be possible for anyone to audit how the container is built and if someone wishes to fork it and build their own containers they are of course welcome to do so.
We do need to iterate rather quickly on these things. Moving forward I hope to start doing at least one release of pixelator each month, so if we need to hand that work of to someone else it will create quite a lot of extra work for us and other, that I would like to avoid.Phil Ewels
04/30/2025, 6:57 AMJames Fellows Yates
04/30/2025, 7:08 AMJames Fellows Yates
04/30/2025, 7:09 AM]], conda:[enabled:true, channels:[conda-forge, bioconda]], shifter:[enabled:false], prov:[enabled:true, overwrite:true, params:[outdir:./results], file:./results/manifest.json], session:[:], executor:[:], runName:golden_goodall, workDir:work, poolSize:16]James Fellows Yates
04/30/2025, 7:09 AMsession.config.conda.enabled?Johan Dahlberg
04/30/2025, 7:10 AM