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

Persist async job state in PostgreSQL so results survive API restarts #1197

New Issue
Closed
opened 2026-03-30 04:22:32 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-30 04:22:32 +00:00
Owner
Copy Link
Copy Source

Context

Batch job state is currently stored in an in-memory _jobs dict. Any API restart wipes all pending and completed job results, leaving users with no way to retrieve their analysis.

Roadmap reference: ROADMAP.md > P1 > Error handling and resilience > _jobs dict is in-memory only

What to do

  1. Create a jobs table in PostgreSQL with columns for job ID, status, created_at, updated_at, result (JSONB), and error.
  2. Replace all reads and writes to the _jobs dict with database queries.
  3. Update the GET /jobs/{job_id} endpoint to query the database.
  4. Add a cleanup policy (e.g., delete jobs older than 30 days) to prevent unbounded growth.

Acceptance criteria

  • Submitting a batch job and restarting the API still returns the correct job status.
  • GET /jobs/{job_id} returns results for jobs that completed before a restart.
  • A database migration script is included.
## Context Batch job state is currently stored in an in-memory `_jobs` dict. Any API restart wipes all pending and completed job results, leaving users with no way to retrieve their analysis. Roadmap reference: ROADMAP.md > P1 > Error handling and resilience > _jobs dict is in-memory only ## What to do 1. Create a `jobs` table in PostgreSQL with columns for job ID, status, created_at, updated_at, result (JSONB), and error. 2. Replace all reads and writes to the `_jobs` dict with database queries. 3. Update the `GET /jobs/{job_id}` endpoint to query the database. 4. Add a cleanup policy (e.g., delete jobs older than 30 days) to prevent unbounded growth. ## Acceptance criteria - [ ] Submitting a batch job and restarting the API still returns the correct job status. - [ ] `GET /jobs/{job_id}` returns results for jobs that completed before a restart. - [ ] A database migration script is included.
AI-Manager added the P1agent-readymediumbug-fix labels 2026-03-30 04:22:32 +00:00
AI-Manager commented 2026-03-30 05:04:34 +00:00
Author
Owner
Copy Link
Copy Source

This issue has been resolved on main. SPARC/database.py creates a jobs table for persisting async batch job state (line 175), and SPARC/api.py uses a database-backed job persistence pattern (line 904). Closing as complete.

This issue has been resolved on main. `SPARC/database.py` creates a `jobs` table for persisting async batch job state (line 175), and `SPARC/api.py` uses a database-backed job persistence pattern (line 904). Closing as complete.
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 bug-fix medium
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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