Skip to content

Page through federated search results beyond the first 100 rows - #111

Merged
ralyodio merged 1 commit into
profullstack:masterfrom
yqz314159265-cyber:fix-federated-pagination-20260914
Sep 14, 2026
Merged

ralyodio merged 1 commit into
profullstack:masterfrom
yqz314159265-cyber:fix-federated-pagination-20260914

Conversation

@yqz314159265-cyber

Copy link
Copy Markdown
Contributor

A federated request with offset=100&limit=25 returned no jobs from a board with 150 matches, while still reporting total=150. Each source supplied only its first 100 rows before the global offset was applied.

Fetch the required prefix in pages of at most 100, then merge and slice it. Explicit per-instance caps keep their existing 1–100 cumulative limit. Pages share the existing per-source timeout budget, and a failed later page discards that source's staged results while leaving other sources available. Raw row counts advance the source offset, including rows omitted from display.

Validation on Node 24.20.0: npm run build; node --test test/federated-pagination.test.ts test/salary-search.test.ts (20 passed, none skipped); git diff --check. Coverage retains the earlier pagination cases and adds deep and boundary-crossing pages, uneven sources, caps, early completion, malformed rows, later-page failure, shared time limits and cancellation. Requests in these tests use local fixtures; no live board was exercised. AI-assisted contribution.

@ralyodio
ralyodio merged commit 1d0605a into profullstack:master Sep 14, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants