Has anyone seen a linting error like below (<link>...
# help
j
Has anyone seen a linting error like below (link)? Working on the 4.1.0 template merge for nf-core/funcscan. (Please ignore all other CI fails, they are due to database download issues.)
Copy code
ERROR    Could not parse Nextflow config for
         '/home/runner/work/funcscan/funcscan'. Possibly because of a Nextflow
         version mismatch?
         Command 'nextflow config -o json /home/runner/work/funcscan/funcscan'
         failed with exit code 1
         Downloading plugin nf-schema@2.7.2
         ERROR ~ No such variable: meta
Error: Process completed with exit code 1.
✅ 1
e
j
Thanks for the related discussions! Helped me solve it. Only 2 modules had such lists of maps in their
modules.config
, I updated them accordingly.
🙌 1
Nevermind. Now that I've found the (temporary) fix, I've decided to adopt @Joon Klaps' solution of using a fixed nextflow version in the linting workflow and wait for the upstream fix. nextflow pet
(This one)
e
yep..this is what the bots had suggested me to do..but do you trust these people with updating??
nextflow zoom 2
joking 😛
t
I am having the same issue, and opted for pinning my nextflow version to
"25.10.4"
. That resolves the issue with the publishDirs, but now linting fails because my linting.yml doesn’t match the template. Fixing that with
nf-core pipelines lint --fix
then removes the version pin in linting.yml (as expected). This is a weird catch 22. How did everyone else make this work? I cannot see the magic that breaks the cycle in the funcscan PR by @Jasmin Frangenberg nor the viralmetagenome PR by @Joon Klaps 😮‍💨 Yet you both have passing tests 😅
I see now that you guys had the linting yml excluded from files_unchanged already, hence why it wasn’t showing up in the PR. homer disappear
homer disappear 2