Closed johanneskoester closed 3 months ago
This has historic reasons, but I agree this needs some fixing.
When Cutadapt is used without an output file name (via -o
), the only choice is to send all FASTA/FASTQ data to stdout and to send everything else (errors, report, other logging) to stderr. For consistency (well, and because it was easier to implement ...), when you provide -o
, the only change is that all this is sent to stdout instead of stderr.
I cannot really make a distinction between logging and the QC report because the log is the report. For example, MultiQC parses the This is cutadapt ...
line to recognize Cutadapt logs, so this needs to be part of the report.
Maybe what prompted you to file this issue is that a command like this (which fails) prints nothing on stderr:
cutadapt -o out.fastq nonexistentfile.fastq > report.log
I agree it makes more sense to always send errors to stderr. Would that resolve the issue for you?
Yes, if errors are on stderr I would be happy :-)
Since I will have to fix the snakemake wrapper for cutadapt: chances for a quick release with that change (then no wrapper change is needed)? Otherwise, I would for now change the wrapper.
Sure, I can make a new release today.
Version 4.7 is out, and the Bioconda recipe update should also get merged soon.
Oh, seen it, thank you!
Cutadapt writes its logging output and errors to STDOUT. According to the docs, I expected report information (qc stats) on STDOUT, but logging and errors on STDERR. Did I misunderstand that?
cutadapt 4.6 insallation via mamba env: