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

Persist job state to PostgreSQL so batch results survive API restarts #1354

New Issue
Closed
opened 2026-03-30 15:22:34 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-30 15:22:34 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap item: P1 Error handling and resilience

The _jobs dict is stored in memory only. Any API restart clears all in-flight and completed job state, making async batch results unavailable to clients.

What to do

  • Create a jobs table in PostgreSQL (columns: job_id, status, created_at, updated_at, result as JSONB, error).
  • Replace all reads/writes to _jobs with database queries.
  • Ensure job creation, status updates, and result writes are transactional.
  • Clean up old completed jobs after a configurable retention period (e.g., 7 days).

Acceptance criteria

  • Restarting the API process does not lose job state for in-progress or completed jobs.
  • GET /jobs/{job_id} returns correct status after a restart.
  • A migration script or Alembic migration is included.
  • Existing batch processing tests pass.
## Context Roadmap item: P1 Error handling and resilience The `_jobs` dict is stored in memory only. Any API restart clears all in-flight and completed job state, making async batch results unavailable to clients. ## What to do - Create a `jobs` table in PostgreSQL (columns: `job_id`, `status`, `created_at`, `updated_at`, `result` as JSONB, `error`). - Replace all reads/writes to `_jobs` with database queries. - Ensure job creation, status updates, and result writes are transactional. - Clean up old completed jobs after a configurable retention period (e.g., 7 days). ## Acceptance criteria - Restarting the API process does not lose job state for in-progress or completed jobs. - `GET /jobs/{job_id}` returns correct status after a restart. - A migration script or Alembic migration is included. - Existing batch processing tests pass.
AI-Manager added the P1agent-readymediumrefactor labels 2026-03-30 15:22:34 +00:00
AI-Manager commented 2026-03-30 16:05:33 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] This issue has already been resolved on the main branch. Verified by code inspection during triage. Closing.

[Repo Manager] This issue has already been resolved on the main branch. Verified by code inspection during triage. Closing.
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#1354
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?