nf-core / nf-core/stats

GitHub Stats Pipeline is DOWN

Open
#163 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 GitHub Stats Pipeline is DOWN (success signal did not arrive on time, grace time passed).

Project: Stats Page
Tags: stats github
Period: 1 day
Total Pings: 1006
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 pygments (1.2MiB)
Downloading dlt (1.1MiB)
Downloading pyarrow (45.3MiB)
Downloading duckdb (19.5MiB)
Downloading setuptools (1.0MiB)
Downloading botocore (14.6MiB)
Downloading pip (1.7MiB)
 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 133ms
2026-08-27 01:27:54,854 - INFO - Starting GitHub data pipeline...
2026-08-27 01:27:54,867 - INFO - Checking initial rate limit status...
2026-08-27 01:27:54,997 - INFO - Rate limit: 4888/5000 remaining (resets at 2026-08-27 02:18:32+00:00)
2026-08-27 01:28:01,495 - INFO - Successfully fetched 201 re
[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 linked Healthchecks.io check and the last ping body to identify where the GitHub Stats Pipeline stopped reporting success. Review the pipeline run output, then verify that a subsequent run completes and the healthcheck receives its success signal on time.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, python
Domain
data-engineering, devops
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.