Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Not a valid path value type: org.codehaus.groovy.runtime.NullObject (null) #283

Closed
mdozmorov opened this issue Sep 10, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@mdozmorov
Copy link

mdozmorov commented Sep 10, 2023

Description of the bug

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.

Command used and terminal output

nextflow run nf-core/smrnaseq --input ${INPUT} \
  --outdir ${DIROUT} \
  -profile 'singularity' \
  --genome GRCh38 \
  --mirtrace_species 'hsa' \
  --protocol 'illumina'

Relevant files

No response

System information

nextflow version 23.04.3.5875
HPC
local
singularity
CentOS 7
2.2.3

@mdozmorov mdozmorov added the bug Something isn't working label Sep 10, 2023
@macrobiotus
Copy link

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.

Screenshot 2023-09-25 at 13 29 35
Screenshot 2023-09-25 at 13 30 17
Screenshot 2023-09-25 at 13 31 25

@apeltzer
Copy link
Member

apeltzer commented Feb 5, 2024

Should be fine with dev now

@apeltzer apeltzer closed this as completed Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants