nf-core / rnaseq

RNA sequencing analysis pipeline using STAR, RSEM, HISAT2 or Salmon with gene/isoform counts and extensive quality control.
https://nf-co.re/rnaseq
MIT License
931 stars 709 forks source link

BBPSPLIT fails cryptically with user errors #1130

Open pinin4fjords opened 1 year ago

pinin4fjords commented 1 year ago

Description of the bug

I had a senior moment and re-submitted an rna-seq run in Seqera Platform, modifying the reference files and not using additional_fasta but forgetting to take out bbsplit_fasta_list and reset skip_bbsplit to true. This caused a failure like

Exception in thread "Thread-7" java.lang.RuntimeException: java.io.EOFException
    at fileIO.ReadWrite.readObject(ReadWrite.java:823)
    at fileIO.ReadWrite.read(ReadWrite.java:1285)
    at fileIO.LoadThread.run(LoadThread.java:30)
Caused by: java.io.EOFException
    at java.base/java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2926)
    at java.base/java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3421)
    at java.base/java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:959)
    at java.base/java.io.ObjectInputStream.(ObjectInputStream.java:397)
    at fileIO.ReadWrite.readObject(ReadWrite.java:818)
    ... 2 more
Exception in thread "Thread-5" java.lang.AssertionError: null, [I@497de40d
    at align2.Block.read(Block.java:148)
    at align2.IndexMaker4$BlockMaker.makeArrays(IndexMaker4.java:140)
    at align2.IndexMaker4$BlockMaker.run(IndexMaker4.java:128)

... and the job just hung.

So despite the ultimate cause being operator error there are two issues:

Command used and terminal output

$ nextflow run 'https://github.com/nf-core/rnaseq'
         -name nostalgic_pare
         -params-file 'https://api.tower.nf/ephemeral/TEPfBKFjWQ0C9XohEadhTA.json'
         -with-tower
         -r dev
         -latest

Relevant files

No response

System information

No response

drpatelh commented 6 months ago

Did we find a fix for this @pinin4fjords ? Saw you removed it from the milestone. Shall we push it to the next one?

pinin4fjords commented 6 months ago

I don't quite know what to do about it, and we're probably not going to go digging into BBMAP to fix it. I'd like to leave it open as an aid for anyone else getting the same error, but I can't see us doing anything about it any time soon, so it shouldn't be on a milestone.

MatthiasZepper commented 6 months ago

Which process was it that failed? The index construction or the actual BB Split mapping?

pinin4fjords commented 6 months ago

Pretty sure it was the actual BBSplit, but now you're asking I'm doubting myself.