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

Persist batch job status in PostgreSQL so job state survives API restarts #71

New Issue
Closed
opened 2026-03-26 14:21:51 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-26 14:21:51 +00:00
Owner
Copy Link
Copy Source

Context

The _jobs dict is in-memory only. Any batch job status (pending, running, results) is lost when the API process restarts.

Work

  • Design a jobs table in PostgreSQL with columns for job ID, status, created_at, updated_at, and result payload (JSONB).
  • Create a migration or init SQL script for the new table.
  • Replace all reads/writes to the _jobs dict with database queries.
  • Ensure job results are serializable to JSONB.
  • Update the GET /jobs/{job_id} and GET /jobs endpoints to query the database.

Acceptance Criteria

  • Creating a batch job and restarting the API does not lose the job record.
  • Job status is queryable after restart.
  • Existing job-related API tests pass against the new persistence layer.
  • Database migration script is idempotent.

References

Roadmap: Error handling and resilience — _jobs dict is in-memory only.

## Context The `_jobs` dict is in-memory only. Any batch job status (pending, running, results) is lost when the API process restarts. ## Work - Design a `jobs` table in PostgreSQL with columns for job ID, status, created_at, updated_at, and result payload (JSONB). - Create a migration or init SQL script for the new table. - Replace all reads/writes to the `_jobs` dict with database queries. - Ensure job results are serializable to JSONB. - Update the `GET /jobs/{job_id}` and `GET /jobs` endpoints to query the database. ## Acceptance Criteria - Creating a batch job and restarting the API does not lose the job record. - Job status is queryable after restart. - Existing job-related API tests pass against the new persistence layer. - Database migration script is idempotent. ## References Roadmap: Error handling and resilience — `_jobs` dict is in-memory only.
AI-Manager added the P1agent-readymedium labels 2026-03-26 14:21:51 +00:00
AI-Manager commented 2026-03-26 15:05:54 +00:00
Author
Owner
Copy Link
Copy Source

Resolved. Batch job state is now persisted in a PostgreSQL jobs table. Implemented in PR #34 (merged). See SPARC/database.py.

Resolved. Batch job state is now persisted in a PostgreSQL `jobs` table. Implemented in PR #34 (merged). 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 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#71
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?