pook/compliancebot

Fork 0

Add 1MB body size limit middleware on POST /api/generate rejecting oversized payloads #355

New issue

Closed

opened 2026-04-10 12:32:56 -04:00 by pook · 1 comment

pook commented

2026-04-10 12:32:56 -04:00

Owner

Add express.json({ limit: '1mb' }) applied to the /api/generate route. Express will automatically return 413 Payload Too Large when exceeded. Ensure the error is caught by the global error handler and returns structured JSON: { error: 'Request body exceeds 1MB limit', requestId }. Add an integration test POSTing a 1.1MB JSON body and asserting 413 status. Replaces stale #308 with exact acceptance criteria.

Generated by CEO Planner (priority: 2)

Add `express.json({ limit: '1mb' })` applied to the /api/generate route. Express will automatically return 413 Payload Too Large when exceeded. Ensure the error is caught by the global error handler and returns structured JSON: `{ error: 'Request body exceeds 1MB limit', requestId }`. Add an integration test POSTing a 1.1MB JSON body and asserting 413 status. Replaces stale #308 with exact acceptance criteria. --- *Generated by CEO Planner (priority: 2)*

pook added the

agent-task

label

2026-04-10 12:32:56 -04:00

agent-bot referenced this issue from a commit

2026-04-10 12:44:35 -04:00

feat: issue #355 add-expressjson-limit-1mb-applied-to-the (agent task agent-ta)

pook referenced this issue

2026-04-10 13:33:43 -04:00

Add global body size limit middleware on all POST routes #383

pook commented

2026-04-10 14:47:43 -04:00

Author

Owner

Bulk-closed 2026-04-10 during pipeline triage.

Context: CEO agent had created 100 open agent-task issues against compliancebot, largely duplicates of each other and of the 50 currently-open PRs. Root cause traced to a git-push race in agent-worker executor (dispatch jobs collided on branch agent/dispatch/* because jobId prefix truncated to literal "dispatch"). Fix deployed: runId is now threaded from Paperclip shim through /dispatch → TaskJob → executor, and branches are keyed on a 12-char unique run key.

What to do next:

Triage the 50 open PRs at https://192.168.183.110:3000/pook/compliancebot/pulls — many are ready to merge
CEO should halt new task creation until open PRs drop below 10
Surviving kept issues: #313, #314, #315, #341, #342, #350, #351, #352 (PR review/merge tasks)

This issue was superseded, not abandoned. Reopen if still relevant after PR triage.

Bulk-closed 2026-04-10 during pipeline triage. **Context:** CEO agent had created 100 open agent-task issues against compliancebot, largely duplicates of each other and of the 50 currently-open PRs. Root cause traced to a git-push race in agent-worker executor (dispatch jobs collided on branch `agent/dispatch/*` because jobId prefix truncated to literal "dispatch"). Fix deployed: runId is now threaded from Paperclip shim through /dispatch → TaskJob → executor, and branches are keyed on a 12-char unique run key. **What to do next:** 1. Triage the 50 open PRs at https://192.168.183.110:3000/pook/compliancebot/pulls — many are ready to merge 2. CEO should halt new task creation until open PRs drop below 10 3. Surviving kept issues: #313, #314, #315, #341, #342, #350, #351, #352 (PR review/merge tasks) This issue was superseded, not abandoned. Reopen if still relevant after PR triage.

pook closed this issue

2026-04-10 14:47:43 -04:00

No labels

agent-task

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

pook/compliancebot#355

No description provided.

Rows
Columns