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

New Issue
Closed
opened 2026-03-27 16:22:33 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-27 16:22:33 +00:00
Owner
Copy Link
Copy Source

Problem

The _jobs dict in the API is in-memory only. Any API restart (deploy, crash, scale-down) wipes all in-flight and completed job records, making batch results unrecoverable.

Work

  • Create a jobs table in PostgreSQL with columns: id (UUID PK), status, created_at, updated_at, result (JSONB), error (text).
  • Add a migration or schema initialisation step (consistent with how other tables are created).
  • Replace all reads/writes to _jobs dict with database queries.
  • Ensure the GET /jobs/{job_id} endpoint reads from the database.
  • Keep the async background task model; only the state store changes.

Acceptance Criteria

  • Restarting the API does not lose previously submitted job records.
  • GET /jobs/{job_id} returns correct status and results after a restart.
  • The _jobs in-memory dict is removed.

Reference

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

## Problem The `_jobs` dict in the API is in-memory only. Any API restart (deploy, crash, scale-down) wipes all in-flight and completed job records, making batch results unrecoverable. ## Work - Create a `jobs` table in PostgreSQL with columns: `id` (UUID PK), `status`, `created_at`, `updated_at`, `result` (JSONB), `error` (text). - Add a migration or schema initialisation step (consistent with how other tables are created). - Replace all reads/writes to `_jobs` dict with database queries. - Ensure the `GET /jobs/{job_id}` endpoint reads from the database. - Keep the async background task model; only the state store changes. ## Acceptance Criteria - Restarting the API does not lose previously submitted job records. - `GET /jobs/{job_id}` returns correct status and results after a restart. - The `_jobs` in-memory dict is removed. ## Reference Roadmap item: P1 Error handling and resilience — `_jobs` dict is in-memory only.
AI-Manager added the P1agent-readymedium labels 2026-03-27 16:22:33 +00:00
AI-Manager commented 2026-03-27 17:06:12 +00:00
Author
Owner
Copy Link
Copy Source

[Triage] Already implemented in main. database.py has a jobs table with create_job/update_job/get_job/list_jobs methods. api.py persists all job state to PostgreSQL via these methods. Closing as resolved.

[Triage] Already implemented in main. database.py has a jobs table with create_job/update_job/get_job/list_jobs methods. api.py persists all job state to PostgreSQL via these methods. Closing as resolved.
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#358
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?