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

Bug: Persist async job state in PostgreSQL so results survive API restarts #713

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

Summary

Job state is stored in an in-memory _jobs dict. Any API restart wipes all pending and completed job results, making async batch operations unreliable in production.

What to do

  • Design a jobs table in PostgreSQL (columns: id, status, created_at, updated_at, result_json, error).
  • Migrate job reads/writes from the _jobs dict to database queries.
  • Ensure in-flight background tasks update job status in the database as they progress.
  • Add a migration script or Alembic revision for the new table.

Acceptance Criteria

  • Restarting the API does not lose job records for running or completed jobs.
  • GET /jobs/{job_id} returns correct status after an API restart.
  • A database migration creates the jobs table cleanly on a fresh schema.
  • Existing batch job tests continue to pass.

Reference

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

## Summary Job state is stored in an in-memory `_jobs` dict. Any API restart wipes all pending and completed job results, making async batch operations unreliable in production. ## What to do - Design a `jobs` table in PostgreSQL (columns: `id`, `status`, `created_at`, `updated_at`, `result_json`, `error`). - Migrate job reads/writes from the `_jobs` dict to database queries. - Ensure in-flight background tasks update job status in the database as they progress. - Add a migration script or Alembic revision for the new table. ## Acceptance Criteria - [ ] Restarting the API does not lose job records for running or completed jobs. - [ ] `GET /jobs/{job_id}` returns correct status after an API restart. - [ ] A database migration creates the `jobs` table cleanly on a fresh schema. - [ ] Existing batch job tests continue to pass. ## Reference Roadmap: P1 Error handling and resilience — `_jobs` dict is in-memory only.
AI-Manager added the P1agent-readymediumbug labels 2026-03-28 16:22:11 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-28 17:03:03 +00:00
AI-Manager commented 2026-03-28 17:05:46 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] Already resolved. Job state persisted in PostgreSQL via create_job/update_job/get_job/list_jobs. Stale jobs marked failed on restart.

Closing as already implemented in the codebase.

[Repo Manager] Already resolved. Job state persisted in PostgreSQL via create_job/update_job/get_job/list_jobs. Stale jobs marked failed on restart. Closing as already implemented in the codebase.
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 bug medium
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#713
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?