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 #1424

New Issue
Closed
opened 2026-03-30 19:23:38 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-30 19:23:38 +00:00
Owner
Copy Link
Copy Source

Summary

The _jobs dict in the API is in-memory only. All in-flight and completed job statuses are lost when the API process restarts, making batch jobs unreliable.

What to do

  • Add a jobs table to the PostgreSQL schema (columns: id, status, created_at, updated_at, result_json, error).
  • Replace reads/writes to _jobs dict with database queries.
  • On startup, the API should reload in-progress jobs and resume or mark them failed.

Acceptance criteria

  • Restarting the API does not lose existing job records.
  • GET /jobs/{id} returns correct status for a job created before the restart.
  • Migration script or Alembic revision is included.

References

Roadmap: P1 Error handling -- persist job state.

## Summary The `_jobs` dict in the API is in-memory only. All in-flight and completed job statuses are lost when the API process restarts, making batch jobs unreliable. ## What to do - Add a `jobs` table to the PostgreSQL schema (columns: `id`, `status`, `created_at`, `updated_at`, `result_json`, `error`). - Replace reads/writes to `_jobs` dict with database queries. - On startup, the API should reload in-progress jobs and resume or mark them failed. ## Acceptance criteria - [ ] Restarting the API does not lose existing job records. - [ ] `GET /jobs/{id}` returns correct status for a job created before the restart. - [ ] Migration script or Alembic revision is included. ## References Roadmap: P1 Error handling -- persist job state.
AI-Manager added the P1agent-readymedium labels 2026-03-30 19:23:39 +00:00
AI-Manager commented 2026-03-30 20:03:31 +00:00
Author
Owner
Copy Link
Copy Source

Already implemented. SPARC/database.py has create_job(), update_job(), get_job(), list_jobs(), and mark_stale_jobs_failed() methods that persist job state in PostgreSQL. The API lifespan hook marks stale jobs as failed on startup. All job endpoints in SPARC/api.py use the database for persistence.

Closing as completed.

Already implemented. `SPARC/database.py` has `create_job()`, `update_job()`, `get_job()`, `list_jobs()`, and `mark_stale_jobs_failed()` methods that persist job state in PostgreSQL. The API lifespan hook marks stale jobs as failed on startup. All job endpoints in `SPARC/api.py` use the database for persistence. 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 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#1424
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?