The Nextstrain command-line interface (CLI)—a program called nextstrain—which aims to provide a consistent way to run and visualize pathogen builds and access Nextstrain components like Augur and Auspice across computing environments such as Docker, Conda, and AWS Batch.
I think this is a delay in the output of logs from nextstrain build, but I'm not sure from why. Is it due to a Python output buffer in print_job_log, or is this a delay further upstream in fetch_stream?
Hmm, nvm, this seems like something more specific to the GH Action workflow.
I was trying things out locally and my local log output is in sync with the logs I see on CloudWatch.
@corneliusroemer flagged a lag in GH Action logs for an AWS Batch job in https://github.com/nextstrain/ncov-ingest/issues/474.
I think this is a delay in the output of logs from
nextstrain build
, but I'm not sure from why. Is it due to a Python output buffer in print_job_log, or is this a delay further upstream in fetch_stream?