fix(actions): runs raw_json is unusable - event_payload bloats 4 runs to 4.3MB #123

Closed
opened 2026-07-15 22:13:57 +00:00 by hexajon · 0 comments
hexajon commented 2026-07-15 22:13:57 +00:00 (Migrated from codeberg.org)

madt_actions action=runs limit=10 raw_json=true on sixfold_space/madtea (2026-07-15) returned 4,333,296 characters for what turned out to be 4 runs - each run object carries its full event_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:

  1. Strip or bound event_payload in raw_json output (drop it by default; a param can opt back in if anyone ever needs it). The formatted text mode is unaffected.
  2. Verify 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

  • raw_json runs output for a typical repo fits comfortably in a tool result (no event_payload blobs).
  • limit behaves as documented.
`madt_actions action=runs limit=10 raw_json=true` on sixfold_space/madtea (2026-07-15) returned 4,333,296 characters for what turned out to be 4 runs - each run object carries its full `event_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: 1. **Strip or bound `event_payload` in raw_json output** (drop it by default; a param can opt back in if anyone ever needs it). The formatted text mode is unaffected. 2. **Verify `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 - raw_json runs output for a typical repo fits comfortably in a tool result (no event_payload blobs). - limit behaves as documented.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sixfold-space/madtea#123
No description provided.