GitHub Stats Pipeline is DOWN

The check GitHub Stats Pipeline is DOWN (received a failure signal).

Project: Stats Page
Tags: stats github
Period: 1 day
Total Pings: 988
Last Ping: Exit status 1, 2 seconds 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 setuptools (1.0MiB)
Downloading pip (1.7MiB)
Downloading pygments (1.2MiB)
Downloading botocore (14.6MiB)
Downloading dlt (1.1MiB)
Downloading duckdb (19.5MiB)
Downloading pyarrow (45.3MiB)
 Downloaded pygments
 Downloaded duckdb
      Built nf-core-stats @ file:///home/runner/work/stats/stats/pipeline
 Downloaded setuptools
 Downloaded pip
 Downloaded dlt
 Downloaded pyarrow
 Downloaded botocore
Installed 63 packages in 126ms
2026-08-19 18:31:00,181 - INFO - Starting GitHub data pipeline...
2026-08-19 18:31:00,194 - INFO - Checking initial rate limit status...
2026-08-19 18:31:00,284 - INFO - Rate limit: 4970/5000 remaining (resets at 2026-08-19 18:56:00+00:00)
2026-08-19 18:31:00,322 - ERROR - Rate limited (403). resour
[truncated]

Start with the GitHub data pipeline run and obtain the complete failure output after the rate-limit error. Trace how GitHub API rate-limit responses are handled and verify a successful Stats Page run and check recovery. Done means the health check receives a success signal.