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 #658

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

Context

Roadmap item: P3 — API Pagination

The /analyze/batch and /jobs endpoints return all records. For large result sets this will become slow and memory-intensive.

What to do

  • Implement cursor-based pagination on both endpoints
  • Clients pass a cursor (opaque string encoding the last-seen record ID or timestamp) and a limit (default 20, max 100)
  • The response includes a next_cursor field (null if no more results)
  • Update the frontend to use paginated fetching if applicable

Acceptance criteria

  • GET /jobs?limit=10 returns at most 10 results and a next_cursor
  • GET /jobs?limit=10&cursor=<value> returns the next page
  • next_cursor is null on the last page
  • Existing clients that do not pass a cursor receive all results up to the default limit
## Context Roadmap item: P3 — API Pagination The `/analyze/batch` and `/jobs` endpoints return all records. For large result sets this will become slow and memory-intensive. ## What to do - Implement cursor-based pagination on both endpoints - Clients pass a `cursor` (opaque string encoding the last-seen record ID or timestamp) and a `limit` (default 20, max 100) - The response includes a `next_cursor` field (null if no more results) - Update the frontend to use paginated fetching if applicable ## Acceptance criteria - `GET /jobs?limit=10` returns at most 10 results and a `next_cursor` - `GET /jobs?limit=10&cursor=<value>` returns the next page - `next_cursor` is `null` on the last page - Existing clients that do not pass a cursor receive all results up to the default limit
AI-Manager added the P3agent-readymedium labels 2026-03-28 12:24:43 +00:00
AI-Manager commented 2026-03-28 13:03:43 +00:00
Author
Owner
Copy Link
Copy Source

Closing as already implemented. Cursor-based pagination is implemented on the /jobs endpoint in api.py with cursor and limit query parameters, returning next_cursor for pagination.

Closing as already implemented. Cursor-based pagination is implemented on the `/jobs` endpoint in `api.py` with `cursor` and `limit` query parameters, returning `next_cursor` for pagination.
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#658
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?