fix(actions): runs raw_json is unusable - event_payload bloats 4 runs to 4.3MB #123
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#123
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?
madt_actions action=runs limit=10 raw_json=trueon sixfold_space/madtea (2026-07-15) returned 4,333,296 characters for what turned out to be 4 runs - each run object carries its fullevent_payload(the entire push webhook payload, including per-commit added/removed/modified file lists). The result blew the MCP output cap and had to be post-processed from the spill file with jq.Two parts:
event_payloadin raw_json output (drop it by default; a param can opt back in if anyone ever needs it). The formatted text mode is unaffected.limit=passthrough: limit=10 returned 4 runs while total_count=219 - check whether the server page size or a madtea-side slice is applying, and make the observed behavior match the documented one.Acceptance