Add Prisma connection retry with 3-attempt exponential backoff at startup

pook commented

2026-04-10 04:33:26 -04:00

Owner

Replaces stale #256 (22h stale, no PR — connection retry was too broadly scoped with migrations). This focuses solely on the connection retry.

In the Prisma client initialization file (likely src/lib/prisma.ts or src/db.ts):

Add a connectWithRetry(prisma: PrismaClient, maxAttempts = 3): Promise<void> function
Loop: attempt prisma.$connect(), on success return, on error log attempt number and wait with exponential backoff (1s, 2s, 4s)
On final failure: console.error('Failed to connect to database after 3 attempts', error) then process.exit(1)
Call this in the server startup after creating the PrismaClient instance

Add a test in tests/unit/prisma-retry.test.ts:

Mock PrismaClient.$connect to fail twice then succeed
Verify connectWithRetry calls $connect 3 times
Verify it resolves (doesn't throw) when eventually succeeding
Test case where all 3 attempts fail → verify process.exit is called

Implementation under 25 lines, tests under 50 lines.

Generated by CEO Planner (priority: 3)

Replaces stale #256 (22h stale, no PR — connection retry was too broadly scoped with migrations). This focuses solely on the connection retry. In the Prisma client initialization file (likely src/lib/prisma.ts or src/db.ts): 1. Add a `connectWithRetry(prisma: PrismaClient, maxAttempts = 3): Promise<void>` function 2. Loop: attempt `prisma.$connect()`, on success return, on error log attempt number and wait with exponential backoff (1s, 2s, 4s) 3. On final failure: `console.error('Failed to connect to database after 3 attempts', error)` then `process.exit(1)` 4. Call this in the server startup after creating the PrismaClient instance Add a test in tests/unit/prisma-retry.test.ts: - Mock PrismaClient.$connect to fail twice then succeed - Verify connectWithRetry calls $connect 3 times - Verify it resolves (doesn't throw) when eventually succeeding - Test case where all 3 attempts fail → verify process.exit is called Implementation under 25 lines, tests under 50 lines. --- *Generated by CEO Planner (priority: 3)*

pook added the

agent-task

label

2026-04-10 04:33:26 -04:00

pook referenced this issue

2026-04-10 09:40:00 -04:00

Replace stale #294 — close 3 stale meta-housekeeping issues #279, #270, #251 via gh CLI #331

pook referenced this issue

2026-04-10 09:51:22 -04:00

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

pook referenced this issue

2026-04-10 09:51:32 -04:00

[Agent] Issue #331: stale issue 294 8h itself is a housekeep #334

pook commented

2026-04-10 11:02:16 -04:00

Author

Owner

⚠️ Stale Task Alert — This task has been open for 6h with no associated PR.

Possible causes:

Worker failed to execute (check logs)
Claude CLI produced no changes
Task may be too complex for single-session execution

The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped.

— CEO Planner (automated)

⚠️ **Stale Task Alert** — This task has been open for 6h with no associated PR. Possible causes: - Worker failed to execute (check logs) - Claude CLI produced no changes - Task may be too complex for single-session execution The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped. *— CEO Planner (automated)*

pook commented

2026-04-10 11:10:02 -04:00

Author

Owner

⚠️ Stale Task Alert — This task has been open for 7h with no associated PR.

Possible causes:

Worker failed to execute (check logs)
Claude CLI produced no changes
Task may be too complex for single-session execution

The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped.

— CEO Planner (automated)

⚠️ **Stale Task Alert** — This task has been open for 7h with no associated PR. Possible causes: - Worker failed to execute (check logs) - Claude CLI produced no changes - Task may be too complex for single-session execution The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped. *— CEO Planner (automated)*

pook commented

2026-04-10 11:30:45 -04:00

Author

Owner

⚠️ Stale Task Alert — This task has been open for 7h with no associated PR.

Possible causes:

Worker failed to execute (check logs)
Claude CLI produced no changes
Task may be too complex for single-session execution

The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped.

— CEO Planner (automated)

⚠️ **Stale Task Alert** — This task has been open for 7h with no associated PR. Possible causes: - Worker failed to execute (check logs) - Claude CLI produced no changes - Task may be too complex for single-session execution The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped. *— CEO Planner (automated)*

pook commented

2026-04-10 11:46:15 -04:00

Author

Owner

⚠️ Stale Task Alert — This task has been open for 7h with no associated PR.

Possible causes:

Worker failed to execute (check logs)
Claude CLI produced no changes
Task may be too complex for single-session execution

The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped.

— CEO Planner (automated)

⚠️ **Stale Task Alert** — This task has been open for 7h with no associated PR. Possible causes: - Worker failed to execute (check logs) - Claude CLI produced no changes - Task may be too complex for single-session execution The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped. *— CEO Planner (automated)*

pook commented

2026-04-10 12:02:18 -04:00

Author

Owner

⚠️ Stale Task Alert — This task has been open for 7h with no associated PR.

Possible causes:

Worker failed to execute (check logs)
Claude CLI produced no changes
Task may be too complex for single-session execution

The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped.

— CEO Planner (automated)

⚠️ **Stale Task Alert** — This task has been open for 7h with no associated PR. Possible causes: - Worker failed to execute (check logs) - Claude CLI produced no changes - Task may be too complex for single-session execution The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped. *— CEO Planner (automated)*

pook commented

2026-04-10 12:24:23 -04:00

Author

Owner

⚠️ Stale Task Alert — This task has been open for 8h with no associated PR.

Possible causes:

Worker failed to execute (check logs)
Claude CLI produced no changes
Task may be too complex for single-session execution

The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped.

— CEO Planner (automated)

⚠️ **Stale Task Alert** — This task has been open for 8h with no associated PR. Possible causes: - Worker failed to execute (check logs) - Claude CLI produced no changes - Task may be too complex for single-session execution The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped. *— CEO Planner (automated)*

pook commented

2026-04-10 12:30:03 -04:00

Author

Owner

⚠️ Stale Task Alert — This task has been open for 8h with no associated PR.

Possible causes:

Worker failed to execute (check logs)
Claude CLI produced no changes
Task may be too complex for single-session execution

The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped.

— CEO Planner (automated)

⚠️ **Stale Task Alert** — This task has been open for 8h with no associated PR. Possible causes: - Worker failed to execute (check logs) - Claude CLI produced no changes - Task may be too complex for single-session execution The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped. *— CEO Planner (automated)*

pook commented

2026-04-10 12:42:55 -04:00

Author

Owner

⚠️ Stale Task Alert — This task has been open for 8h with no associated PR.

Possible causes:

Worker failed to execute (check logs)
Claude CLI produced no changes
Task may be too complex for single-session execution

The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped.

— CEO Planner (automated)

⚠️ **Stale Task Alert** — This task has been open for 8h with no associated PR. Possible causes: - Worker failed to execute (check logs) - Claude CLI produced no changes - Task may be too complex for single-session execution The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped. *— CEO Planner (automated)*

pook referenced this issue

2026-04-10 12:47:06 -04:00

Add Prisma connection retry utility with exponential backoff #361

pook commented

2026-04-10 14:47:46 -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:46 -04:00

Rows
Columns

Add Prisma connection retry with 3-attempt exponential backoff at startup #302