https://nf-co.re logo
Join Slack
Powered by
Nextflow source test CI failed
# nextflow-nightly-tests
s
Nextflow source test CI failed
Nextflow source test CI failed
😱 2
j
this looks like a problem with nf-schema?
p
Paging @Nicolas Vannieuwkerke !
also yay that this worked yay wait
n
Interesting! Is this urgent? Otherwise I'll leave this for when I'm back on Tuesday
p
it's relatively urgent, as this is the last edge release before the next stable, which I think is going out middle of next week. So if we need anything to change on the nextflow side then we need to know ASAP
@Ben Sherman when you're up, would you mind taking a look at this please, as Nico is away?
Copy code
N E X T F L O W  ~  version 25.09.1-edge
Downloading plugin nf-schema@2.5.1
Launching `nf-core-testpipeline/main.nf` [condescending_monod] DSL2 - revision: 5cb1e1644f
ERROR ~ Class definition not found: nextflow/config/schema/ConfigScope

 -- Check script 'nf-core-testpipeline/workflows/testpipeline.nf' at line: 8 or see '.nextflow.log' file for more details
Error: Process completed with exit code 1.
I guess that this is something to do with recent changes to the config parser
n
Okay I'll take a look today!
p
only if it's easy, if you're vacation then leave it!
At least until Ben is awake and can respond
it's still documented here though, so itäs weird that it's saying that it's not found 😕
n
I'm just on a couple of days off to use my leftover day offs 😛. Currently looking at it, but I can't replicate it in pipelines I have locally so now investigating if it's maybe something in the template
yeah maybe it is a Nextflow bug?
p
link for myself to click more easily: https://github.com/nf-core/tools/actions/runs/18578367780
n
Okay I'm confused, I followed the exact same steps as the action, but locally and it succeeded without issue
🤔 1
I triggered a rerun to see if it happens again
Still happening on the action, I see that the latest Nextflow version gets built in there so maybe that's the issue here? Locally I just pulled the latest edge version using the 
NXF_VER
variable
I'm at a loss right now 😁 let's see if @Ben Sherman has any ideas 😛 I can pick it back up tomorrow if needed
m
i guess the difference it that you pull the latest released version, while this pulls and builds the latest code from 
master
this 1
n
ah yes that could be it indeed!
anyways seems like a Nextflow bug to me
p
If anyone is able to reproduce locally, doing a 
git bisect
to find the upstream commit would be super useful
This one ran with build from 
ef0d2d6010b491ef9769bf8b1a4f7e32ff443a4d
I've also flagged this to the Nextflow dev team by the way, but no-one picked it up yet as everyone is swamped
b
we had to make a breaking change for plugin developers @Phil Ewels you were looking at edge docs but if you're building from 
master
then you need to look at latest: https://nextflow.io/docs/latest/developer/config-scopes.html#definition
@Nicolas Vannieuwkerke I was going to reach out to you shortly anyway. We'll need to cut new minor versions for nf-prov and nf-schema that require >=25.10 both for this change and also to enable the language server support like I mentioned to you recently but it's not urgent, enjoy your time off 😄
it's also documented in the 25.10 migration notes
n
Thanks! I'll do a quick release when the new Nextflow version releases
I got a PR ready with all changes needed for when the new Nextflow version releases: https://github.com/nextflow-io/nf-schema/pull/180
b
We made a patch to Nextflow that should keep it compatible with existing plugins. Looks like it is working since there hasn't been any more failures here
🎉 4
very nice 1
Open in Slack
PreviousNext
Powered by