nf-core / nf-core/stats

Slack Stats Pipeline is DOWN

Open
#162 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

healthchecks
Dominant language
Python
Stars
2
Forks
4
PR merge metrics
No merged PRs in 30d

Description

The check Slack Stats Pipeline is DOWN (success signal did not arrive on time, grace time passed).

Project: Stats Page
Tags: stats dlt
Period: 1 day
Total Pings: 1110
Last Ping: Success, 1 day, 1 hour ago
Last Ping Body:

Downloading cpython-3.10.21-linux-x86_64-gnu (download) (28.1MiB)
 Downloaded cpython-3.10.21-linux-x86_64-gnu (download)
Using CPython 3.10.21
Creating virtual environment at: .venv
   Building nf-core-stats @ file:///home/runner/work/stats/stats/pipeline
Downloading pip (1.7MiB)
Downloading pygments (1.2MiB)
Downloading dlt (1.1MiB)
Downloading duckdb (19.5MiB)
Downloading setuptools (1.0MiB)
Downloading pyarrow (45.3MiB)
Downloading botocore (14.6MiB)
 Downloaded pygments
 Downloaded duckdb
 Downloaded setuptools
 Downloaded pip
 Downloaded dlt
      Built nf-core-stats @ file:///home/runner/work/stats/stats/pipeline
 Downloaded pyarrow
 Downloaded botocore
Installed 63 packages in 113ms
2026-08-27 01:27:57,968 - INFO - Starting Slack data pipeline...
2026-08-27 01:27:57,983 - INFO - Initializing Slack client with token starting with: xoxp-...
2026-08-27 01:27:58,147 - INFO - Successfully authenticated as: edmund.a.miller in workspace: nf-core
2026-08-27 01:28:04,007 - INFO - Retrie
[truncated]

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Slack Stats Pipeline health check and the latest run output in this issue, then inspect the Stats Page pipeline entry point and its daily execution path. Identify why the success signal stopped arriving and verify that a complete run produces a timely success ping again.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data-engineering, observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.