Skip to content

Fix duplicate and dropped rows in maintainer queue pagination#420

Open
diksha78dev wants to merge 1 commit into
Coder-s-OG-s:mainfrom
diksha78dev:fix/pagination-duplication
Open

Fix duplicate and dropped rows in maintainer queue pagination#420
diksha78dev wants to merge 1 commit into
Coder-s-OG-s:mainfrom
diksha78dev:fix/pagination-duplication

Conversation

@diksha78dev

Copy link
Copy Markdown
Contributor

Summary

Fixes an issue where the maintainer PR and issue queues fetch overlapping sets of rows, causing duplicates and dropping rows during client-side tier sorting.

Type of Change

  • Bug fix

Related Issue

Closes #398

What was changed?

  • Updated getMaintainerPrQueue and getMaintainerIssueQueue to fetch strictly non-overlapping 100-row database blocks.
  • Mapped page offsets (page % 4) to slice exactly 25 rows out of each block.
  • Updated the hasMore threshold to accurately check both the remaining slice bounds and the upstream database limit.

Checklist

  • My code follows the project structure and conventions
  • I tested this locally (npm run dev)
  • No hardcoded secrets or credentials
  • I have updated documentation if needed

@vercel

vercel Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

@diksha78dev is attempting to deploy a commit to the codersogs-3057's projects Team on Vercel.

A member of the Team first needs to authorize it.

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.

Maintainer PR and issue queue pagination can duplicate or drop rows across pages

1 participant