Error running with "Error nextflow.config:298:14: Unexpected input"
Nobody has claimed this yet.
- Dominant language
- Nextflow
- Stars
- 229
- Forks
- 141
- Avg merge
- 13h 41m
- Merged PRs (30d)
- 1
Description
Description of the bug
I am using nextflow version 26.04.1 and java version 21.0.6.
Running ./nextflow run nf-core/atacseq -profile test,singularity
N E X T F L O W ~ version 26.04.1
Pulling nf-core/atacseq ...
WARN: Cannot read project manifest -- Cause: Config parsing failed
downloaded from https://github.com/nf-core/atacseq.git
Error nextflow.config:298:14: Unexpected input: '('
│ 298 | def check_max(obj, type) {
╰ | ^
ERROR ~ Config parsing failed
-- Check '.nextflow.log' file for details
Command used and terminal output
Relevant files
No response
System information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing ./nextflow run nf-core/atacseq -profile test,singularity with Nextflow 26.04.1 and Java 21.0.6, then inspect nextflow.config around line 298 where def check_max(obj, type) is reported. Compare the configuration syntax with the supported Nextflow version and confirm that the test profile runs without the parsing error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- bioinformatics
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100