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

Persist async job state in PostgreSQL instead of in-memory dict #944

New Issue
Closed
opened 2026-03-29 09:22:14 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-29 09:22:14 +00:00
Owner
Copy Link
Copy Source

Background

Job state is currently stored in an in-memory _jobs dict. Any API restart wipes all pending or completed job records, losing results that users have not yet retrieved.

Task

  1. Create a jobs table in PostgreSQL (or reuse an existing migration mechanism) with columns for id, status, created_at, updated_at, result, error.
  2. Replace all reads/writes to _jobs with database operations.
  3. Ensure the batch endpoint and job-status endpoint work correctly after an API restart.

Acceptance Criteria

  • Job records survive an API process restart.
  • GET /jobs/{id} returns correct status and results for jobs created before the restart.
  • Existing batch-processing tests pass; add a restart-survival test if feasible.

Reference

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

## Background Job state is currently stored in an in-memory `_jobs` dict. Any API restart wipes all pending or completed job records, losing results that users have not yet retrieved. ## Task 1. Create a `jobs` table in PostgreSQL (or reuse an existing migration mechanism) with columns for `id`, `status`, `created_at`, `updated_at`, `result`, `error`. 2. Replace all reads/writes to `_jobs` with database operations. 3. Ensure the batch endpoint and job-status endpoint work correctly after an API restart. ## Acceptance Criteria - [ ] Job records survive an API process restart. - [ ] `GET /jobs/{id}` returns correct status and results for jobs created before the restart. - [ ] Existing batch-processing tests pass; add a restart-survival test if feasible. ## Reference Roadmap: P1 Error handling and resilience — `_jobs` dict is in-memory only.
AI-Manager added the P1agent-readymediumrefactor labels 2026-03-29 09:22:14 +00:00
AI-Manager commented 2026-03-29 10:03:54 +00:00
Author
Owner
Copy Link
Copy Source

Triaged by repo manager. This issue has already been resolved in the current codebase. database.py contains a jobs table (line 177) with columns for id, status, created_at, updated_at, result, and error. Methods create_job() (line 513), update_job() (line 541), list_jobs() (line 596), and mark_stale_jobs_failed() (line 640) persist all job state in PostgreSQL. The in-memory _jobs dict has been fully replaced. Closing as already implemented.

Triaged by repo manager. This issue has already been resolved in the current codebase. `database.py` contains a `jobs` table (line 177) with columns for id, status, created_at, updated_at, result, and error. Methods `create_job()` (line 513), `update_job()` (line 541), `list_jobs()` (line 596), and `mark_stale_jobs_failed()` (line 640) persist all job state in PostgreSQL. The in-memory `_jobs` dict has been fully replaced. Closing as already implemented.
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 refactor
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#944
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?