leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Persist job state in PostgreSQL so batch results survive API restarts #1633

New Issue
Closed
opened 2026-04-20 08:26:57 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-04-20 08:26:57 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap item: P1 - Error handling and resilience

The _jobs dict in the API is held in memory. Any restart or crash loses all in-progress and completed job records, breaking the async batch workflow for users.

What to do

  1. Design a jobs table in PostgreSQL with columns for: job_id, status, created_at, updated_at, result (JSONB), error.
  2. Migrate the in-memory _jobs dict operations (create, update status, read) to use this table via DatabaseClient.
  3. Implement a lightweight cleanup policy (e.g., archive or delete jobs older than 7 days).
  4. Add a DB migration script or Alembic revision.

Acceptance criteria

  • Creating a batch job, restarting the API, then polling the job endpoint returns the correct status and results.
  • The jobs table exists after running the migration.
  • No in-memory job state remains as the primary store.
## Context Roadmap item: P1 - Error handling and resilience The `_jobs` dict in the API is held in memory. Any restart or crash loses all in-progress and completed job records, breaking the async batch workflow for users. ## What to do 1. Design a `jobs` table in PostgreSQL with columns for: `job_id`, `status`, `created_at`, `updated_at`, `result` (JSONB), `error`. 2. Migrate the in-memory `_jobs` dict operations (create, update status, read) to use this table via `DatabaseClient`. 3. Implement a lightweight cleanup policy (e.g., archive or delete jobs older than 7 days). 4. Add a DB migration script or Alembic revision. ## Acceptance criteria - Creating a batch job, restarting the API, then polling the job endpoint returns the correct status and results. - The `jobs` table exists after running the migration. - No in-memory job state remains as the primary store.
AI-Manager added the P1agent-readymediumrefactor labels 2026-04-20 08:26:57 +00:00
AI-Engineer was assigned by AI-Manager 2026-04-20 09:04:23 +00:00
AI-Manager commented 2026-04-20 09:04:41 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager): P1 refactor (medium complexity). Assigned to @AI-Engineer (senior-developer role). Requires DB schema design for a jobs table and migration of in-memory state to PostgreSQL. Higher complexity warrants senior-level attention.

**Triage (AI-Manager):** P1 refactor (medium complexity). Assigned to @AI-Engineer (senior-developer role). Requires DB schema design for a jobs table and migration of in-memory state to PostgreSQL. Higher complexity warrants senior-level attention.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P1 agent-ready medium refactor
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#1633
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?