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

Persist async job state to PostgreSQL so results survive API restarts #309

New Issue
Closed
opened 2026-03-27 12:22:45 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-27 12:22:45 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap item: P1 Error handling and resilience

The _jobs dict lives in process memory. Any API restart (deployment, crash, OOM kill) loses all in-progress and completed job records, leaving clients with no way to retrieve results.

Work Required

  • Add a jobs table to the PostgreSQL schema (columns: job_id, status, created_at, updated_at, result_json, error)
  • Replace all reads and writes to the _jobs dict with database queries
  • Ensure job creation, status updates, and result storage are all persisted
  • Add a migration or CREATE TABLE IF NOT EXISTS statement that runs at startup

Acceptance Criteria

  • Creating a batch job and restarting the API still returns the job status and results via the /jobs/{id} endpoint
  • Job listing (/jobs) reflects all historical jobs from the database
  • No regressions in existing API tests
## Context Roadmap item: P1 Error handling and resilience The `_jobs` dict lives in process memory. Any API restart (deployment, crash, OOM kill) loses all in-progress and completed job records, leaving clients with no way to retrieve results. ## Work Required - Add a `jobs` table to the PostgreSQL schema (columns: `job_id`, `status`, `created_at`, `updated_at`, `result_json`, `error`) - Replace all reads and writes to the `_jobs` dict with database queries - Ensure job creation, status updates, and result storage are all persisted - Add a migration or `CREATE TABLE IF NOT EXISTS` statement that runs at startup ## Acceptance Criteria - Creating a batch job and restarting the API still returns the job status and results via the `/jobs/{id}` endpoint - Job listing (`/jobs`) reflects all historical jobs from the database - No regressions in existing API tests
AI-Manager added the P1agent-readymedium labels 2026-03-27 12:22:45 +00:00
AI-Manager commented 2026-03-27 13:03:33 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved in the fork's main branch. Already implemented in PR #34 (feat(jobs): persist async batch job state in PostgreSQL). See SPARC/database.py jobs table.

Closing as completed.

This issue has already been resolved in the fork's main branch. Already implemented in PR #34 (feat(jobs): persist async batch job state in PostgreSQL). See SPARC/database.py jobs table. Closing as completed.
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
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#309
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?