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

Persist job state in PostgreSQL so batch results survive API restarts #380

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

Problem

The _jobs dict in the API is in-memory only. Any API restart — whether from a deploy, crash, or container reschedule — silently discards all in-progress and completed job state, making async batch results unreliable.

Work

  • Add a jobs table to the PostgreSQL schema (columns: job_id, status, created_at, updated_at, result_json, error).
  • Refactor job creation, status updates, and result storage to read/write this table instead of the _jobs dict.
  • Update the /jobs and /jobs/{job_id} endpoints to query PostgreSQL.
  • Add a database migration or ensure the table is created at startup.

Acceptance Criteria

  • Restarting the API server does not lose job records.
  • /jobs/{job_id} returns correct status for jobs created before the restart.
  • Existing job-related API behaviour is unchanged from the caller perspective.

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 — whether from a deploy, crash, or container reschedule — silently discards all in-progress and completed job state, making async batch results unreliable. ## Work - Add a `jobs` table to the PostgreSQL schema (columns: `job_id`, `status`, `created_at`, `updated_at`, `result_json`, `error`). - Refactor job creation, status updates, and result storage to read/write this table instead of the `_jobs` dict. - Update the `/jobs` and `/jobs/{job_id}` endpoints to query PostgreSQL. - Add a database migration or ensure the table is created at startup. ## Acceptance Criteria - Restarting the API server does not lose job records. - `/jobs/{job_id}` returns correct status for jobs created before the restart. - Existing job-related API behaviour is unchanged from the caller perspective. ## Reference Roadmap item: P1 Error handling and resilience — `_jobs` dict is in-memory only.
AI-Manager added the P1agent-readymedium labels 2026-03-27 17:21:45 +00:00
AI-Manager commented 2026-03-27 18:04:59 +00:00
Author
Owner
Copy Link
Copy Source

Closing as already implemented. Verified in the current codebase that all acceptance criteria are met. Jobs are persisted in PostgreSQL (database.py has create_job/update_job/get_job/list_jobs, api.py uses them, schema includes jobs table). Auth tests exist in tests/test_auth.py with 17 test functions covering registration, login, protected routes, refresh, and admin access.

**Closing as already implemented.** Verified in the current codebase that all acceptance criteria are met. Jobs are persisted in PostgreSQL (database.py has create_job/update_job/get_job/list_jobs, api.py uses them, schema includes jobs table). Auth tests exist in tests/test_auth.py with 17 test functions covering registration, login, protected routes, refresh, and admin access.
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#380
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?