You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently you can get verbose module (and presumably subworkflow) nf-test verbose/debugging logs by asking for --verbose at the tools level.
I find this unintuitive as if I'm looking for nf-test logs, I wouldn't ask at the nf-core level as I'm not interested in nf-core logs at the same time.
e.g. I want to find out why my nf-test failed
nf-core --verbose modules test <module>
doesn't make sense to me, but rather
nf-core modules test --verbose <module>
## OR
nf-core modules test <module> --verbose
Does, as it 'feels' like I'm assking the --verbose log for the test itself. However this gives an error of an unrecognised option
Description of feature
Currently you can get verbose module (and presumably subworkflow) nf-test verbose/debugging logs by asking for
--verbose
at the tools level.I find this unintuitive as if I'm looking for nf-test logs, I wouldn't ask at the nf-core level as I'm not interested in nf-core logs at the same time.
e.g. I want to find out why my nf-test failed
doesn't make sense to me, but rather
Does, as it 'feels' like I'm assking the
--verbose
log for the test itself. However this gives an error of an unrecognised optionMore details here: https://nfcore.slack.com/archives/CE5LG7WMB/p1701779689455179
That said the 'mixed'
--verbose
isn't so messy. As a fast work around could just alias amodules test
level verbose to the general nf-core one.The text was updated successfully, but these errors were encountered: