pook/compliancebot

Fork 0

Add graceful shutdown handler to complete in-flight document generations #55

New issue

Closed

opened 2026-04-08 15:16:30 -04:00 by pook · 1 comment

pook commented

2026-04-08 15:16:30 -04:00

Owner

Document generation involves LLM API calls that can take 5-15 seconds. An abrupt shutdown loses the generation and the user's payment may already be captured.

Implement:

Register SIGTERM and SIGINT handlers.
Stop accepting new requests (respond 503), but let in-flight generation requests finish.
Hard timeout at 30 seconds — log and force-exit if requests are still pending.
Emit structured log: { event: 'shutdown_start', pending: N } and { event: 'shutdown_done', duration_ms }.

Acceptance criteria:

In-flight document generations complete during shutdown.
503 returned for new requests during drain.
Clean exit after all requests complete or hard timeout.

Generated by CEO Planner (priority: 3)

Document generation involves LLM API calls that can take 5-15 seconds. An abrupt shutdown loses the generation and the user's payment may already be captured. Implement: 1. Register SIGTERM and SIGINT handlers. 2. Stop accepting new requests (respond 503), but let in-flight generation requests finish. 3. Hard timeout at 30 seconds — log and force-exit if requests are still pending. 4. Emit structured log: `{ event: 'shutdown_start', pending: N }` and `{ event: 'shutdown_done', duration_ms }`. Acceptance criteria: - In-flight document generations complete during shutdown. - 503 returned for new requests during drain. - Clean exit after all requests complete or hard timeout. --- *Generated by CEO Planner (priority: 3)*

pook added the

agent-task

label

2026-04-08 15:16:30 -04:00

pook referenced this issue

2026-04-08 23:31:16 -04:00

Add graceful shutdown handler to drain in-flight document generations before exit #171

agent-bot referenced this issue from a commit

2026-04-08 23:39:49 -04:00

feat: add graceful shutdown to prevent lost API calls during deploy

pook referenced this issue from a pull request that will close it,

2026-04-08 23:42:40 -04:00

feat: graceful shutdown to prevent lost LLM API calls #173

pook referenced this issue

2026-04-09 06:08:04 -04:00

Close 10 stale tasks that have matching PRs or duplicate scope #251

pook referenced this issue

2026-04-09 06:12:19 -04:00

Add graceful shutdown handler to drain in-flight document generations before exit #171

pook referenced this issue

2026-04-09 06:12:29 -04:00

[Agent] Issue #251: 10 issues are stale but many have duplic #253

pook commented

2026-04-10 14:48:30 -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:48:30 -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#55

No description provided.

Rows
Columns