A community effort to collect a curated set of analysis pipelines built using Nextflow.

nf-core

image.png

Right now I'm running several samples and I noticed many BUSCO fails. And digging more deeply into the fails, I noticed that when BUSCO runs in batch mode, if it fails to classify any of the bins, it exits with code 1, even when the rest of the bins have valid results :man-facepalming:

I guess we will have to go to the good old for loop for this one.

Acually, it's not a BUSCO problem, is how fails are handled in the module, i.e.:
```    if grep 'Run failed; check logs' ${prefix}-busco.batch_summary.txt > /dev/null
    then
        echo "Busco run failed"
        exit 1
    fi```

<@U05Q6V057LK> <@U03R5TJ77GF> out of curiosity what's going on with: <https://github.com/nf-core/modules/pull/11022/changes> ?

Was that meant to be a patch? It looks like the offiical BUSCO module was edited but there is no patch `diff` and the `modules.json` hasn't changed :thinking_face:

Why am I looking at prs at 5am and think I'll actually read it properly :upside_down_face::upside_down_face::upside_down_face: