Skip to content

fix(alerts): Show capped pagination counts as lower bounds - #121500

Open
sentry-junior[bot] wants to merge 5 commits into
masterfrom
fix/alerts-capped-pagination-count
Open

fix(alerts): Show capped pagination counts as lower bounds#121500
sentry-junior[bot] wants to merge 5 commits into
masterfrom
fix/alerts-capped-pagination-count

Conversation

@sentry-junior

@sentry-junior sentry-junior Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Show capped Alerts pagination totals as lower bounds instead of presenting the paginator's 1,000-row count ceiling as an exact total.

Scoped to the Alerts list only. The caption mirrors the Issues list pattern with local tct and QueryCount in [total].

Why the default ceiling fallback

OffsetPaginator counts hits but does not expose max_hits, so production workflows responses omit X-Max-Hits. Without a fallback, early pages (including the first page) treated X-Hits: 1000 as exact. This list now defaults maxHits to 1000 when the header is missing, and still treats deep pages past X-Hits as capped.

Requested by Nick Meisenheimer.

--

View Junior Session [Sentry]

Co-Authored-By: Nick Meisenheimer <nicholas.meisenheimer@sentry.io>
@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Aug 7, 2026
@souredoutlook
souredoutlook marked this pull request as ready for review August 7, 2026 00:16
@souredoutlook
souredoutlook requested review from a team as code owners August 7, 2026 00:16
Co-Authored-By: Nick Meisenheimer <nicholas.meisenheimer@sentry.io>
@souredoutlook souredoutlook added the Trigger: getsentry tests Once code is reviewed: apply label to PR to trigger getsentry tests label Aug 7, 2026
Comment thread static/app/views/automations/list.tsx Outdated
Keep the lower-bound marker in the [total] slot so translations cannot leave the + stranded, without changing the shared pagination helper.
@github-actions github-actions Bot removed the Trigger: getsentry tests Once code is reviewed: apply label to PR to trigger getsentry tests label Aug 7, 2026
When pagination walks past the reported X-Hits count, treat the total as a lower bound even if X-Max-Hits is missing from the response.

Co-Authored-By: Nick Meisenheimer <nicholas.meisenheimer@sentry.io>

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 749123f. Configure here.

Comment thread static/app/views/automations/list.tsx
OffsetPaginator omits X-Max-Hits, so early Alerts pages never knew the 1000-row ceiling. Default maxHits to 1000 so first-page totals can still render as lower bounds.

Co-Authored-By: Nick Meisenheimer <nicholas.meisenheimer@sentry.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant