https://nf-co.re logo
Join Slack
Powered by
So I think `nextflow log` prints a log of the Next...
# infrastructure
p
So I think 
nextflow log
prints a log of the Nextflow runs that have happened. It does not print the log output of a run. So we were right to be surprised @mashehu @Yuxin Ning @Edmund - this doesn't already exist 😅
a
This makes sense though right? The log output is by default in a file which gets rotated 
nextflow.log.N
and eventually will be overwritten. I'm not sure how nextflow could track that even if it wanted to, it would require storing the log output in something less ephemeral?
p
Sorry, some context - in the meeting we were discussing about filtering log files to remove debug statements to make them more token-efficient for LLMs
Then we remembered the 
nextflow log
command already exists and looked at the help output and saw 
-filter
which talks about filtering by status and were like "huh, it already exists!"
but it doesn't - it's filtering lists of runs for status, not the logfile contents. So was just clearing that up
Actually it has nothing to do with log files, somewhat confusingly
This was following on from discussion about this PR
a
Nice PR!
p
And now another 🫢 😅
s
Oh please, lets remove those stupid 
debug
statements by default
😅 1
p
I like having them there. It's the same behaviour in MultiQC, always printing the verbose log to a file. Then it's there on disk for reference if ever you need it (can't go back otherwise).
This hopefully gives the best of both worlds - you choose how verbose you want the log to be when reading it
2 Views
Open in Slack
PreviousNext
Powered by