nextflow-io / nextflow-io/nextflow

Boolean parameter validation failure in nf-core/rnaseq 3.26.0 with Nextflow 26.04

Open
#7,411 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Groovy
Stars
3.5k
Forks
811
Avg merge
2d 11h
Merged PRs (30d)
61

Description

Hi,

I encountered a parameter validation issue when running nf-core/rnaseq 3.26.0 with Nextflow 26.04.1.

Environment:

Nextflow: 26.04.1 build 12646
nf-core/rnaseq: 3.26.0
Java: 17
Executor: Singularity
OS: Ubuntu Linux

Command:

nextflow run nf-core/rnaseq \
-r 3.26.0 \
-profile singularity \
--input /path/to/samplesheet.csv \
--fasta /path/to/GRCh38.fa \
--gtf /path/to/GRCh38.gtf \
--outdir rnaseq_results \
--aligner star_salmon \
--remove_ribo_rna
The pipeline stops during parameter validation:
ERROR ~ Validation of pipeline parameters failed!

The following invalid input values have been detected:

--remove_ribo_rna (true): Value is [string] but should be [boolean]
The same command works normally with Nextflow 25.10.2 using the same nf-core/rnaseq version (3.26.0).

It seems that the boolean parameter passed from the command line is interpreted as a string in Nextflow 26.04.1, causing nf-schema validation to fail.

Could you please check whether this is a compatibility issue between Nextflow 26.04.1 and nf-schema validation?

Thanks.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported command with nf-core/rnaseq 3.26.0 under Nextflow 26.04.1, then compare its parameter handling with Nextflow 25.10.2. Trace the validation path for --remove_ribo_rna and the nf-schema integration; done means the same boolean input validates correctly without regressing older behavior. No source file or test is named in the report.

Written by the indexing model from the issue text.

Assessment

Tech stack
groovy
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.