A community effort to collect a curated set of analysis pipelines built using Nextflow.

nf-core

I'm using the example <https://nf-co.re/rnavar/1.0.0/docs/usage/#:~:text=An%20example%20samplesheet%20has%20been%20provided%20with%20the%20pipeline.|samplesheet> from the docs and getting this issue if anyone can help resolve this:
```╰─ nextflow run nf-core/rnavar --input samplesheet.csv --genome GRCh38 -profile docker

Nextflow 25.04.6 is available - Please consider updating your version to it

 N E X T F L O W  ~ version 24.10.5

Pulling nf-core/rnavar ...
 downloaded from <https://github.com/nf-core/rnavar.git>
Launching `<https://github.com/nf-core/rnavar>` [zen_edison] DSL2 - revision: 0a9036c82b [master]

Downloading plugin nf-schema@2.4.2
ERROR ~ Module compilation error
- file : /Users/aqib/.nextflow/assets/nf-core/rnavar/./workflows/rnavar.nf
- cause: Variable `Channel` already defined in the process scope @ line 129, column 31.
    def umi_extracted_reads = Channel.empty()
                 ^

Module compilation error
- file : /Users/aqib/.nextflow/assets/nf-core/rnavar/./workflows/rnavar.nf
- cause: Variable `Channel` already defined in the process scope @ line 148, column 31.
    def interval_list_split = Channel.empty()
                 ^

Module compilation error
- file : /Users/aqib/.nextflow/assets/nf-core/rnavar/./workflows/rnavar.nf
- cause: Variable `Channel` already defined in the process scope @ line 224, column 35.
      def bam_variant_calling = Channel.empty()
                   ^

Module compilation error
- file : /Users/aqib/.nextflow/assets/nf-core/rnavar/./workflows/rnavar.nf
- cause: Variable `Channel` already defined in the process scope @ line 321, column 35.
      def haplotypecaller_vcf = Channel.empty()
                   ^

Module compilation error
- file : /Users/aqib/.nextflow/assets/nf-core/rnavar/./workflows/rnavar.nf
- cause: Variable `Channel` already defined in the process scope @ line 343, column 29.
        def final_vcf = Channel.empty()
                ^

5 errors```

Updating to the newest Nextflow version should fix this issue, this is a known bug in everything lower than 25

Could you try a more recent Nextflow version