Hello <!channel>! We are approaching the next tool...
# tools
j
Hello @channel! We are approaching the next tools release πŸš€ πŸ“† Planned date: ~in 2 weeks This version will come with a big pipeline template change: πŸ§ͺ nf core adding pipeline level nf-test! πŸš€ After adding nf-test to some pipelines who volunteered, it's time to extend this to all nf-core pipelienes. nf-test helps with making sure the pipeline produces the same output every time you make a new modification. To make this new addition as smooth as possible for pipeline developers, we plan to... β€’ have the usual blog post with more background and how to handle the different changes and possible merge conflicts β€’ record video tutorials going through the template updates β€’ organize #weekly-helpdesk sessions to go through the updates together πŸ‘€ You can view a list of other changes in the CHANGELOG πŸ“£ As usual, reach out if you have any doubt, question or concern Cheers from the <!subteam^S08LAB76NBU>
πŸ‘ 5
party dino 5
deal with infra 23
πŸ‘πŸΌ 1
πŸŽ‰ 16
j
Thanks for the early announcement!
j
Any chance release will happen before metaomics the nf-test fest on the 11th of June??? πŸ‘€πŸ‘€πŸ‘€
m
high chances imo
☝🏻 1
j
tenor_gif294422191132980432.gif
🀣 1
party cowboy 1
m
Has there already been a discussion internally about the
-C
flag of the
process.shell
config in the pipeline template?
Copy code
"-C",         // No clobber - prevent output redirection from overwriting files.
It has broken the
.command.trace
functionality of Nextflow 25.04.x. While it was now fixed on the Nextflow side, there is no released version with that change yet, therefore I wonder if we should keep that in the template? See e.g. this issue and that one.
p
This fix ☝🏻 is about to be released as both a patch release but also backported to at least 24.10.x stable in Nextflow
😍 1
j
Good to know, I would think that the no clobber is a good idea for nextflow to do by default anyway IMO
p
I also suggested that but Paolo was very un-keen
m
So there is no action required on the nf-core site? Admittedly, I also do not know why it was added in the first place...
j
I also suggested that but Paolo was very un-keen
Why so?
p
Because changing the base bash command for all Nextflow pipelines everywhere is a pretty major change
Large potential for unexpected problems
(as we have seen..!)
j
So there is no action required on the nf-core site? Admittedly, I also do not know why it was added in the first place...
@Mahesh Binzer-Panchal added it I believe. I know multiple cases of bad redirects overwriting input files
Because changing the base bash command for all Nextflow pipelines everywhere is a pretty major change
Fair point, could be opt in 'strict' mode though
p
I guess, but that doesn't sound so different to what we're doing already tbh
j
But would keep Nextflow devs more aware of it, to prevent what just happened now 😬
Anyway doesn't matter so much now
m
I am entirely neutral here, I was just reminded of that
-C
flag complication by a reply on a GitHub issue yesterday and wanted to make sure it is given some consideration before the new release of tools.
❀️ 2
p
But would keep Nextflow devs more aware of it, to prevent what just happened now
Yup, but we're already solving this in other ways. For example the new nightly build-Nextflow-run-nf-core-pipeline GitHub action that I set up recently (currently running on my fork, but will be on #tools once the action hits
main
after the coming release)
πŸš€ 2
πŸ‘ 1