jasidhu
06/29/2026, 10:11 PMError modules.config:314:128: Unexpected input: '='
│ 314 | ame, "panel_resources/${filename}", panel_resource_creation = true) },
╰ | ^
ERROR ~ Config parsing failed
i haven't found resources on what's causing this and how to get around this— wondering if anyone here is able to help. thanks in advance!
edit: i ran nextflow run nf-core/oncoanalyser -profile test,singularity --outdir results to test my installation and got the same error; i don't know what could be causing this.Stephen Watts
06/30/2026, 3:24 AMBeatriz Sá Vinhas
06/30/2026, 7:52 AMmodules.config , no? Simply having true (omitting function argument name) should fix this bug.jasidhu
06/30/2026, 4:40 PMnextflow run nf-core/oncoanalyser -profile test,singularity --outdir results
@Beatriz Sá Vinhas i haven't changed any of the config files that come with the pipeline but omitting the function argument name raises a similar error
Error modules.config:338:20: Unexpected input: '('
│ 338 | def get_saveas_path(meta, task, filename, path, panel_resource_creatio
╰ | ^
ERROR ~ Config parsing failed
could this be because nextflow strict syntax doesn't allow functions in config files [source]?Stephen Watts
06/30/2026, 10:39 PMStephen Watts
06/30/2026, 10:39 PMNXF_SYNTAX_PARSER=v1 nextflow run nf-core/oncoanalyser -latest -revision 2.3.0Stephen Watts
06/30/2026, 10:39 PMBeatriz Sá Vinhas
07/01/2026, 8:01 AMoncoanalyser (which makes it not support strict syntax like @Stephen Watts mentioned), not in your config! 🙂jasidhu
07/02/2026, 5:08 PM