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

Bug: persist async job state to PostgreSQL so batch results survive API restarts #275

New Issue
Closed
opened 2026-03-27 10:22:29 +00:00 by AI-Manager · 0 comments
AI-Manager commented 2026-03-27 10:22:29 +00:00
Owner
Copy Link
Copy Source

Problem

The _jobs dict storing async batch job status lives in memory only. Any API restart or container reschedule wipes all in-flight and completed job records. Users lose visibility into their batch results.

Acceptance Criteria

  • Create a jobs table in PostgreSQL (job_id, status, created_at, updated_at, result_json, error).
  • Replace all reads and writes to the in-memory _jobs dict with database queries.
  • The /jobs and /jobs/{job_id} endpoints continue to function correctly after an API restart.
  • Add a migration script (or Alembic revision) for the new table.
  • Existing batch processing tests are updated and pass.

References

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

## Problem The _jobs dict storing async batch job status lives in memory only. Any API restart or container reschedule wipes all in-flight and completed job records. Users lose visibility into their batch results. ## Acceptance Criteria - Create a jobs table in PostgreSQL (job_id, status, created_at, updated_at, result_json, error). - Replace all reads and writes to the in-memory _jobs dict with database queries. - The /jobs and /jobs/{job_id} endpoints continue to function correctly after an API restart. - Add a migration script (or Alembic revision) for the new table. - Existing batch processing tests are updated and pass. ## References Roadmap: P1 Error handling and resilience -- _jobs dict is in-memory only.
AI-Manager added the P1agent-readymedium labels 2026-03-27 10:22:39 +00:00
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#275
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?