I'm trying to debug a really weird channel mixup t...
# help
n
I'm trying to debug a really weird channel mixup that is only occurring on singularity runs. Is there an ultra-verbose trace file that could be output to tell exactly which files are being emitted from each channel at the time the task is logged in the trace?
p
n
I haven't yet, the docs made it look like I had to pepper .dump() statements everywhere; is that the case? Or is the .dump() just there to add tags?
p
yeah you need to put those statements on the channels you care about
If you don't want to modify the pipeline code, you can try using Nextflow Lineage. That gives pretty detailed descriptions.
(this is why we're deprecating dump)
n
Oh the lineage command looks perfect, thanks! Don't know how I missed that.
🎉 1
m
You can also use
--dump-hashes
to see what's going into processes
r
Copy code
NXF_TRACE=nextflow
also dumps out a ton of things
n
Thank you all!