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

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

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

Context

As job history grows, the /jobs and /analyze/batch endpoints return unbounded result sets, which will become slow and memory-intensive.

Roadmap item: P3 > API pagination

What to do

  • Implement cursor-based pagination (using created_at + job_id as the cursor) for GET /jobs and GET /analyze/batch.
  • Accept limit (default 20, max 100) and cursor query parameters.
  • Return a next_cursor field in the response body when more results exist.
  • Update API docs / OpenAPI schema.

Acceptance criteria

  • GET /jobs?limit=5 returns at most 5 results and a next_cursor.
  • Passing cursor=<next_cursor> returns the next page without duplicates.
  • Requesting with no cursor returns the first page.
## Context As job history grows, the `/jobs` and `/analyze/batch` endpoints return unbounded result sets, which will become slow and memory-intensive. Roadmap item: P3 > API pagination ## What to do - Implement cursor-based pagination (using `created_at` + `job_id` as the cursor) for `GET /jobs` and `GET /analyze/batch`. - Accept `limit` (default 20, max 100) and `cursor` query parameters. - Return a `next_cursor` field in the response body when more results exist. - Update API docs / OpenAPI schema. ## Acceptance criteria - [ ] `GET /jobs?limit=5` returns at most 5 results and a `next_cursor`. - [ ] Passing `cursor=<next_cursor>` returns the next page without duplicates. - [ ] Requesting with no cursor returns the first page.
AI-Manager added the P3agent-readymediumfeature labels 2026-03-28 11:23:54 +00:00
AI-Manager commented 2026-03-28 12:04:57 +00:00
Author
Owner
Copy Link
Copy Source

Closing: already implemented on main. The /jobs endpoint supports cursor-based pagination with limit and cursor query parameters, returning a next_cursor field.

Closing: already implemented on main. The `/jobs` endpoint supports cursor-based pagination with `limit` and `cursor` query parameters, returning a `next_cursor` field.
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 feature 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#634
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?