Skip to content

fix(github): use PAGE_SIZE for jobs collector to avoid 502 on large runs - #9316

Open
cedriclecoz wants to merge 2 commits into
apache:mainfrom
cedriclecoz:main
Open

cedriclecoz wants to merge 2 commits into
apache:mainfrom
cedriclecoz:main

Conversation

@cedriclecoz

@cedriclecoz cedriclecoz commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

⚠️ Pre Checklist

Please complete ALL items in this checklist, and remove before submitting

  • I have read through the Contributing Documentation.
  • I have added relevant tests.
  • I have added relevant documentation.
  • I will add labels to the PR, such as pr-type/bug-fix, pr-type/feature-development, etc.

Summary

This PR switches cicd_job_collector.go from the hard-coded PageSize: 100 to the existing PAGE_SIZE constant (30), which cicd_run_collector.go already uses to avoid oversized responses.

Does this close any open issues?

Closes #9315

Other Information

Verified in my setup: a repo that had failed Collect Job Runs on every run since 2026-10-23 completed in ~3 min with per_page=30 (6,293 job pages, no 502s). Its PR counts in DevLake now match GitHub exactly.

GitHub's /actions/runs/{id}/jobs endpoint times out and returns 502
with per_page=100 on workflow runs with many jobs (~70+), which
permanently fails Collect Job Runs and blocks PR conversion for the
repo. Reuse PAGE_SIZE (30), as cicd_run_collector already does to
avoid oversized responses (apache#3199).
fix(github): reduce workflow jobs page size
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug][GitHub] Collect Job Runs fails permanently on HTTP 502 for workflow runs with many jobs (PageSize hard-coded to 100)

1 participant