https://nf-co.re logo
Join Slack
Powered by
Yeah it's a bug in Nextflow 25.10.x. 26.04.0 works...
# team-maintainers
n
Yeah it's a bug in Nextflow 25.10.x. 26.04.0 works 😛
j
Sooo.. what's the fix right now?
n
I would prefer just bumping Nextflow but we need to make sure it doesn't break more than now
j
It's either bump Nextflow or revert what you did I think, all module PRs will fail until we do one or the other
or yes, change the CI to not be impacted by the issue
n
Yeah I would prefer my change would not be reverted as it's needed for strict syntax compatibility in pipelines 😅
Let's try bumping Nextflow? All modules should be strict syntax compatible by now anyways
j
sure, I need to dash out for something- up for doing that?
n
Aight 🙂
thankyou 1
j
Thanks!
Y'all OK if we merge this so modules PRs pass again?
j
Ehhh, I sort of feel modules version should match whatever is in the pipelien template for compatibility
But I don't have a super strong reason, just feeling
j
Would you rather we revert the strict syntax stuff that broke it?
j
consistency* not compatibility
Would you rather we revert the strict syntax stuff that broke it?
Yeah sort of. But I don't know what the context is 😬
But like I said, I don't have a strong argument, but maybe ping teh channel/give a bit more time to make a decision (and in the meantime I would say yes, revert the breaking change to get things working again)
j
Context: https://github.com/nf-core/modules/pull/11532 Innocent-looking, but created a failure that's currently blocking all modules PRs. Hence why I'm keen to sort it rather than discuss for a day.
j
I would then yeah revert that change IMO
it's arguably jumping ahead from what we are 'officially' supporting
n
Hmm okay... What if we just bump the nextflow version of the linting? It's basically a bug in 25.10.x
The code is functional it's just a mistake in the linter
j
sounds legit
3 Views
Open in Slack
PreviousNext
Powered by