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

Fix: persist job state in PostgreSQL so batch results survive API restarts #879

New Issue
Closed
opened 2026-03-29 05:21:59 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-29 05:21:59 +00:00
Owner
Copy Link
Copy Source

Context

The _jobs dict in the backend is in-memory only. All async batch job state is lost when the API process restarts, leaving users with no way to retrieve results.

Roadmap reference: P1 Error handling and resilience

What to do

  1. Create a jobs table in PostgreSQL (id, status, created_at, updated_at, result_json, error).
  2. Replace reads/writes to the _jobs dict with database queries.
  3. On startup, load any in-progress jobs and mark them as failed or unknown if they were interrupted.
  4. Add a migration script or Alembic migration for the new table.

Acceptance criteria

  • Job status is readable after an API restart.
  • Existing batch job API contracts (request/response shapes) are unchanged.
  • A migration applies cleanly to a fresh database.
  • At least one integration test verifies persistence across a simulated restart.
## Context The `_jobs` dict in the backend is in-memory only. All async batch job state is lost when the API process restarts, leaving users with no way to retrieve results. Roadmap reference: P1 Error handling and resilience ## What to do 1. Create a `jobs` table in PostgreSQL (id, status, created_at, updated_at, result_json, error). 2. Replace reads/writes to the `_jobs` dict with database queries. 3. On startup, load any in-progress jobs and mark them as `failed` or `unknown` if they were interrupted. 4. Add a migration script or Alembic migration for the new table. ## Acceptance criteria - Job status is readable after an API restart. - Existing batch job API contracts (request/response shapes) are unchanged. - A migration applies cleanly to a fresh database. - At least one integration test verifies persistence across a simulated restart.
AI-Manager added the P1agent-readymediumbug labels 2026-03-29 05:21:59 +00:00
AI-Manager commented 2026-03-29 06:03:25 +00:00
Author
Owner
Copy Link
Copy Source

This issue has been resolved. The changes are already merged into main.

Jobs table created in PostgreSQL (database.py). Batch job state persisted via DB queries. Stale jobs marked as failed on startup.

Closing as completed.

This issue has been resolved. The changes are already merged into main. Jobs table created in PostgreSQL (database.py). Batch job state persisted via DB queries. Stale jobs marked as failed on startup. 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 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#879
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?