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
When using the nextflow log command, there is no duration and status for a running pipeline.
This was noticed when running the Nextflow ATAC-seq pipeline.
One of the ATAC-seq pipeline maintainers asked that this issue be reported to the Nextflow repository.
Initially reported here: nf-core/atacseq#400
Steps to reproduce the problem
nextflow log
Program output
$ nextflow log
TIMESTAMP DURATION RUN NAME STATUS REVISION ID SESSION ID COMMAND
2025-01-11 00:35:49 - trusting_liskov - 1a1dbe52ff fbe1700b-6ff3-4475-8b9e-b00e118903b1 nextflow run nf-core/atacseq --input ./exp2_sample_sheet.csv --outdir ./results
Environment
Nextflow version: v24.10.3
Hardware: Desktop
Executor: Local
Container engine: Docker 27.4.1
OS: Ubuntu 22.04.5 LTS x86_64
Version of nf-core/atacseq: 2.1.2
The text was updated successfully, but these errors were encountered:
Bug report
Expected behavior and actual behavior
When using the
nextflow log
command, there is no duration and status for a running pipeline.This was noticed when running the Nextflow ATAC-seq pipeline.
One of the ATAC-seq pipeline maintainers asked that this issue be reported to the Nextflow repository.
Initially reported here: nf-core/atacseq#400
Steps to reproduce the problem
nextflow log
Program output
Environment
Nextflow version: v24.10.3
Hardware: Desktop
Executor: Local
Container engine: Docker 27.4.1
OS: Ubuntu 22.04.5 LTS x86_64
Version of nf-core/atacseq: 2.1.2
The text was updated successfully, but these errors were encountered: