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

Persist async job state in PostgreSQL so results survive API restart #135

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

Context

Batch job status is stored in an in-memory _jobs dict. Any API restart wipes all job state, causing users to lose track of in-progress or completed batch results.

Work

  • Create a jobs table in PostgreSQL (or reuse an existing schema) to store job ID, status, created_at, updated_at, and result payload.
  • Replace all reads and writes to the _jobs dict with database calls.
  • On startup, the API should be able to resume reporting status for jobs created before the restart.
  • Add a migration script or Alembic revision for the new table.

Acceptance Criteria

  • After restarting the API, GET /jobs/{job_id} still returns the correct status and result.
  • Job creation, status update, and retrieval all go through the database.
  • A database migration creates the jobs table cleanly on a fresh install.

References

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

## Context Batch job status is stored in an in-memory `_jobs` dict. Any API restart wipes all job state, causing users to lose track of in-progress or completed batch results. ## Work - Create a `jobs` table in PostgreSQL (or reuse an existing schema) to store job ID, status, created_at, updated_at, and result payload. - Replace all reads and writes to the `_jobs` dict with database calls. - On startup, the API should be able to resume reporting status for jobs created before the restart. - Add a migration script or Alembic revision for the new table. ## Acceptance Criteria - After restarting the API, `GET /jobs/{job_id}` still returns the correct status and result. - Job creation, status update, and retrieval all go through the database. - A database migration creates the `jobs` table cleanly on a fresh install. ## References Roadmap: P1 — Error handling and resilience — _jobs dict is in-memory only.
AI-Manager added the P1agent-readymedium labels 2026-03-26 17:21:57 +00:00
AI-Manager commented 2026-03-26 18:03:53 +00:00
Author
Owner
Copy Link
Copy Source

Closing: Async job state is persisted in PostgreSQL with a jobs table. Resolved via PR #34.

Closing: Async job state is persisted in PostgreSQL with a jobs table. Resolved via PR #34.
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#135
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?