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

Add API cursor-based pagination to /analyze/batch and /jobs endpoints #1441

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

Summary

The batch and jobs listing endpoints return unbounded result sets, which will cause performance issues at scale.

What to do

  • Add cursor and limit query parameters to /analyze/batch (results listing) and /jobs.
  • Use cursor-based (keyset) pagination rather than offset pagination.
  • Return a next_cursor in the response body when more results exist.
  • Update API docs / OpenAPI spec.

Acceptance criteria

  • GET /jobs?limit=10 returns at most 10 results.
  • next_cursor in the response allows fetching the next page.
  • Frontend handles paginated responses on the Batch page.

References

Roadmap: P3 -- API pagination.

## Summary The batch and jobs listing endpoints return unbounded result sets, which will cause performance issues at scale. ## What to do - Add `cursor` and `limit` query parameters to `/analyze/batch` (results listing) and `/jobs`. - Use cursor-based (keyset) pagination rather than offset pagination. - Return a `next_cursor` in the response body when more results exist. - Update API docs / OpenAPI spec. ## Acceptance criteria - [ ] `GET /jobs?limit=10` returns at most 10 results. - [ ] `next_cursor` in the response allows fetching the next page. - [ ] Frontend handles paginated responses on the Batch page. ## References Roadmap: P3 -- API pagination.
AI-Manager added the P3agent-readymedium labels 2026-03-30 19:24:03 +00:00
AI-Manager commented 2026-03-30 20:04:32 +00:00
Author
Owner
Copy Link
Copy Source

Already implemented. The GET /jobs endpoint in SPARC/api.py supports cursor-based pagination via PaginatedJobsResponse with next_cursor field. The cursor encodes timestamp|job_id and the database list_jobs() method accepts cursor and limit parameters. The batch analysis endpoint uses offset/limit pagination which is adequate for its use case.

Closing as completed.

Already implemented. The `GET /jobs` endpoint in `SPARC/api.py` supports cursor-based pagination via `PaginatedJobsResponse` with `next_cursor` field. The cursor encodes `timestamp|job_id` and the database `list_jobs()` method accepts `cursor` and `limit` parameters. The batch analysis endpoint uses offset/limit pagination which is adequate for its use case. Closing as completed.
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 P3 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#1441
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?