nf-core / nf-core/stats

GitHub Stats Pipeline is DOWN

Open
#136 0 comments 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 (received a failure signal).

Project: Stats Page
Tags: stats github
Period: 1 day
Total Pings: 832
Last Ping: Exit status 1, now
Last Ping Body:

Downloading cpython-3.10.20-linux-x86_64-gnu (download) (28.0MiB)
 Downloaded cpython-3.10.20-linux-x86_64-gnu (download)
Using CPython 3.10.20
Creating virtual environment at: .venv
   Building nf-core-stats @ file:///home/runner/work/stats/stats/pipeline
Downloading botocore (14.6MiB)
Downloading duckdb (19.5MiB)
Downloading pygments (1.2MiB)
Downloading pyarrow (45.3MiB)
Downloading setuptools (1.0MiB)
Downloading pip (1.7MiB)
Downloading dlt (1.1MiB)
 Downloaded pygments
 Downloaded setuptools
 Downloaded pip
 Downloaded dlt
 Downloaded duckdb
      Built nf-core-stats @ file:///home/runner/work/stats/stats/pipeline
 Downloaded pyarrow
 Downloaded botocore
Installed 63 packages in 119ms
2026-06-23 12:37:03,340 - INFO - Starting GitHub data pipeline...
2026-06-23 12:37:03,353 - INFO - Checking initial rate limit status...
2026-06-23 12:37:03,585 - INFO - Rate limit: 4219/5000 remaining (resets at 2026-06-23 13:03:46+00:00)
2026-06-23 12:37:03,684 - ERROR - Rate limit exhausted. Rese
[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 GitHub Stats Pipeline failure output in this issue, especially the rate-limit exhaustion after the initial check. Inspect the Stats Page pipeline run and its GitHub API usage; done means the pipeline completes successfully and the health check receives a success signal.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, python
Domain
data-engineering, observability
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.