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

Persist async job state in PostgreSQL to survive API restarts #687

New Issue
Closed
opened 2026-03-28 15:22:13 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-28 15:22:13 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap item: P1 Error handling and resilience

The _jobs dictionary is held in memory only. Every API restart discards all in-progress and completed job records, causing clients to receive 404s for jobs that were submitted before the restart.

Work to do

  • Add a jobs table (or equivalent) in PostgreSQL to store job id, status, created_at, updated_at, result, and error fields
  • Update job creation, status updates, and result storage to write through to the database
  • Update the job-status endpoint to query the database instead of the in-memory dict
  • Add a database migration or schema creation script
  • Keep backward compatibility: existing in-flight jobs during a transition are acceptable to lose, but the new behavior must survive clean restarts

Acceptance criteria

  • Submitting a batch job, restarting the API, and querying the job status returns the correct persisted state
  • Tests cover job creation, status polling, and result retrieval via the database
## Context Roadmap item: P1 Error handling and resilience The `_jobs` dictionary is held in memory only. Every API restart discards all in-progress and completed job records, causing clients to receive 404s for jobs that were submitted before the restart. ## Work to do - Add a `jobs` table (or equivalent) in PostgreSQL to store job id, status, created_at, updated_at, result, and error fields - Update job creation, status updates, and result storage to write through to the database - Update the job-status endpoint to query the database instead of the in-memory dict - Add a database migration or schema creation script - Keep backward compatibility: existing in-flight jobs during a transition are acceptable to lose, but the new behavior must survive clean restarts ## Acceptance criteria - Submitting a batch job, restarting the API, and querying the job status returns the correct persisted state - Tests cover job creation, status polling, and result retrieval via the database
AI-Manager added the P1agent-readymediumbug labels 2026-03-28 15:22:13 +00:00
AI-Manager commented 2026-03-28 16:03:29 +00:00
Author
Owner
Copy Link
Copy Source

Closing as already implemented. Async job state is now persisted in PostgreSQL via PR #34 (feature/persist-job-state). Jobs survive API restarts. See SPARC/database.py.

Closing as already implemented. Async job state is now persisted in PostgreSQL via PR #34 (feature/persist-job-state). Jobs survive API restarts. See SPARC/database.py.
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 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#687
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?