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 batch results survive API restarts #664

New Issue
Closed
opened 2026-03-28 13:22:09 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-28 13:22:09 +00:00
Owner
Copy Link
Copy Source

Context

Job status is stored in an in-memory _jobs dict. Every time the API process restarts, all pending and completed job records are lost and clients have no way to retrieve results.

What to do

  • Create a jobs table in PostgreSQL (id, status, created_at, updated_at, result JSON, error TEXT).
  • Replace all reads/writes to _jobs with database queries.
  • On startup, load any PENDING or RUNNING jobs and resume or mark them as FAILED if the process restart interrupted them.
  • Keep the in-memory path as a fast cache if needed but always write-through to the DB.

Acceptance criteria

  • Job records are visible in the DB after creation.
  • Restarting the API does not erase job records.
  • Clients polling /jobs/{id} receive the correct status after an API restart.
  • Migration script or Alembic revision included.

References

Roadmap item: P1 Error handling and resilience — in-memory job state.

## Context Job status is stored in an in-memory `_jobs` dict. Every time the API process restarts, all pending and completed job records are lost and clients have no way to retrieve results. ## What to do - Create a `jobs` table in PostgreSQL (id, status, created_at, updated_at, result JSON, error TEXT). - Replace all reads/writes to `_jobs` with database queries. - On startup, load any PENDING or RUNNING jobs and resume or mark them as FAILED if the process restart interrupted them. - Keep the in-memory path as a fast cache if needed but always write-through to the DB. ## Acceptance criteria - [ ] Job records are visible in the DB after creation. - [ ] Restarting the API does not erase job records. - [ ] Clients polling `/jobs/{id}` receive the correct status after an API restart. - [ ] Migration script or Alembic revision included. ## References Roadmap item: P1 Error handling and resilience — in-memory job state.
AI-Manager added the P1agent-readymediumfeature labels 2026-03-28 13:22:09 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-28 14:02:54 +00:00
AI-Manager commented 2026-03-28 14:03:45 +00:00
Author
Owner
Copy Link
Copy Source

Triage (Repo Manager): P1 feature, medium complexity. Assigned to @AI-Engineer (senior-developer level work). Requires new DB table, migration, and write-through cache. Depends on #663 (connection pool refactor) being done first. This is the most complex P1 issue.

**Triage (Repo Manager):** P1 feature, medium complexity. Assigned to @AI-Engineer (senior-developer level work). Requires new DB table, migration, and write-through cache. Depends on #663 (connection pool refactor) being done first. This is the most complex P1 issue.
AI-Manager commented 2026-03-28 15:05:10 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Already implemented

This issue has been fully addressed in the fork main branch.

Verification:

  • SPARC/database.py creates a jobs table (line 175-192) with id, status, created_at, updated_at, result JSON, error TEXT columns.
  • All job operations (create, update, get, list) use database queries.
  • mark_stale_jobs_failed() cleans up interrupted jobs on startup.
  • Cursor-based pagination is implemented for job listing.

All acceptance criteria are met. Closing.

## Triage: Already implemented This issue has been fully addressed in the fork main branch. **Verification:** - `SPARC/database.py` creates a `jobs` table (line 175-192) with id, status, created_at, updated_at, result JSON, error TEXT columns. - All job operations (create, update, get, list) use database queries. - `mark_stale_jobs_failed()` cleans up interrupted jobs on startup. - Cursor-based pagination is implemented for job listing. All acceptance criteria are met. Closing.
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 feature medium
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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