@ralfduerr As a workaround for now, you can redirect nextstrain
's stdin to /dev/null
(instead of your terminal):
nextstrain build . --configfile builds_first.yaml --dag </dev/null | dot -Tpdf > dag.pdf
@ralfduerr As a workaround for now, you can redirect nextstrain
's stdin to /dev/null
(instead of your terminal):
nextstrain build . --configfile builds_first.yaml --dag </dev/null | dot -Tpdf > dag.pdf
Hi both,
The new command with </dev/null worked out perfectly! Since you filed a bug, there is probably no need to copy all the outputs Victor asked for (happy to do though if it helps in any way).
Sorry that I forgot to start a new topic for this. Next time I’ll do
Is there a chance to receive a notification when the filed bugs are resolved or should I just check the links from time to time?
Other than that, all was perfectly addressed! Many thanks to both of you!
Happy to help! Indeed, no need anymore to copy the outputs asked for by Victor.
If you have a GitHub account, you can “subscribe” to the bug (button on the right hand side) and get notifications on all activity, including resolution.
@ralfduerr Both the original permission denied error and the stdout vs. stderr issue with --dag
you encountered should be resolved in the just-released Nextstrain CLI 3.1.1 (see changes).
That’s awesome!!
Many thanks for letting me know!