You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WARN: Input tuple does not match input set cardinality declared by process `NFCORE_SMRNASEQ:SMRNASEQ:MIRDEEP2:MIRDEEP2_RUN` -- offending value: /path/to/work/eb/4e5e3a3fa9f24739561950cae26c27/genome.edited.fa
ERROR ~ Error executing process > 'NFCORE_SMRNASEQ:SMRNASEQ:MIRDEEP2:MIRDEEP2_RUN (1)'
Caused by:
Not a valid path value type: org.codehaus.groovy.runtime.NullObject (null)
This error is reproducible after nextflow clean nf-core/smrnaseq and restarting in the new folder. I'm running the latest nextflow and the pipeline (2.2.3). Skipping this step with --skip_mirdeep helps, but without it the error persists.
Dear all, thank you for working on this pipeline. I can confirm this from here. Admittedly I keep checking for version 2.2.4 as 2.2.3 doesn't seem to work very well ever since the miRbase links changed.
Description of the bug
This error is reproducible after
nextflow clean nf-core/smrnaseq
and restarting in the new folder. I'm running the latest nextflow and the pipeline (2.2.3). Skipping this step with--skip_mirdeep
helps, but without it the error persists.Command used and terminal output
Relevant files
No response
System information
nextflow version 23.04.3.5875
HPC
local
singularity
CentOS 7
2.2.3
The text was updated successfully, but these errors were encountered: