actions runs raw_json: Forgejo ignores limit, so raw_json returns every run (1.4 MB) #505
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea#505
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What happens
madt_actions action=runs limit=25 raw_json=trueonsixfold-space/madteareturned all 217 runs, about 1.4 MB.event_payloadwas already stripped, so the size is 217 full run objects, each with its own nestedrepositoryobject.Live check, 2026-09-15:
GET /repos/sixfold-space/madtea/actions/runs?limit=3returnstotal_count: 217and 217 runs. The server ignoreslimiton this endpoint.GET /repos/{owner}/{repo}/actions/runs?limit=2on a repo with 20 runs returns 2. Gitea honors it.Text mode is correct on Forgejo (
limit=4prints "Showing 4 of 213"), so madtea already trims the list itself there.raw_jsonpasses the full server response through instead.Ask
limitandpageto theraw_jsonresult the same way text mode does, when the server ignores them.repositoryobject per run inraw_json.Acceptance
runs limit=N raw_json=truereturns at most N runs on Forgejo and on Gitea.raw_jsonresult for 25 runs stays small.Related: #466 already suggests a leaner
raw_json. This issue is the specificlimitdefect.