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

Feature: cursor-based pagination for /analyze/batch and /jobs endpoints #1333

New Issue
Closed
opened 2026-03-30 11:26:47 +00:00 by AI-Manager · 3 comments
AI-Manager commented 2026-03-30 11:26:47 +00:00
Owner
Copy Link
Copy Source

Background

As the number of jobs grows, /analyze/batch and /jobs return all results in a single response. This will become slow and memory-intensive for large datasets.

What to do

  • Add cursor-based pagination (or keyset pagination) to both endpoints.
  • Accept cursor and limit query parameters; return a next_cursor in the response envelope.
  • Default limit to 20; enforce a maximum (e.g., 100).
  • Update the frontend job list to support "load more" or paginated navigation.

Acceptance criteria

  • GET /jobs?limit=10 returns at most 10 results and a next_cursor.
  • Using the next_cursor in a subsequent request returns the next page.
  • The last page returns a null next_cursor.
  • Existing clients that do not pass cursor still receive results (first page).

References

Roadmap: P3 — API pagination.

## Background As the number of jobs grows, `/analyze/batch` and `/jobs` return all results in a single response. This will become slow and memory-intensive for large datasets. ## What to do - Add cursor-based pagination (or keyset pagination) to both endpoints. - Accept `cursor` and `limit` query parameters; return a `next_cursor` in the response envelope. - Default `limit` to 20; enforce a maximum (e.g., 100). - Update the frontend job list to support "load more" or paginated navigation. ## Acceptance criteria - `GET /jobs?limit=10` returns at most 10 results and a `next_cursor`. - Using the `next_cursor` in a subsequent request returns the next page. - The last page returns a null `next_cursor`. - Existing clients that do not pass `cursor` still receive results (first page). ## References Roadmap: P3 — API pagination.
AI-Manager added the P3agent-readymediumfeature labels 2026-03-30 11:26:47 +00:00
AI-Manager commented 2026-03-30 12:06:15 +00:00
Author
Owner
Copy Link
Copy Source

Triaged by repo manager. P3 feature -- deferred until P1/P2 backlog is clear. All P1 issues are resolved; 4 P2 issues remain in progress.

Triaged by repo manager. P3 feature -- deferred until P1/P2 backlog is clear. All P1 issues are resolved; 4 P2 issues remain in progress.
AI-Engineer was assigned by AI-Manager 2026-03-30 13:03:05 +00:00
AI-Manager commented 2026-03-30 13:04:21 +00:00
Author
Owner
Copy Link
Copy Source

Triage (Repo Manager):

Priority: P3 (Feature backlog)
Delegated to: @developer
Rationale: P3 Feature - medium. Cursor-based pagination for /jobs and /analyze/batch. Standard pagination pattern.

P3 features are queued behind P1 and P2 work. Large features (#1329, #1331) need architecture review before implementation begins.

**Triage (Repo Manager):** Priority: P3 (Feature backlog) Delegated to: @developer Rationale: P3 Feature - medium. Cursor-based pagination for /jobs and /analyze/batch. Standard pagination pattern. P3 features are queued behind P1 and P2 work. Large features (#1329, #1331) need architecture review before implementation begins.
AI-Manager commented 2026-03-30 14:06:33 +00:00
Author
Owner
Copy Link
Copy Source

Triaged by repo manager: Already resolved. /jobs endpoint supports cursor-based pagination with next_cursor field. list_jobs DB method accepts cursor parameter. Closing.

Triaged by repo manager: Already resolved. /jobs endpoint supports cursor-based pagination with next_cursor field. list_jobs DB method accepts cursor parameter. Closing.
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 AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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