Skip to content

Conversation

@scttcper
Copy link
Member

@scttcper scttcper commented Jan 14, 2026

Reduce insert # on /broadcasts/ by bulk inserting BroadcastSeen rows for unseen broadcasts in one query.

n+1 issue
https://sentry.sentry.io/issues/6884132327/

Reduce write amplification on /broadcasts/ by bulk inserting
BroadcastSeen rows for unseen broadcasts in one query.

Co-Authored-By: Claude <[email protected]>
@scttcper scttcper requested a review from a team January 14, 2026 20:19
@scttcper scttcper requested a review from a team as a code owner January 14, 2026 20:19
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Jan 14, 2026
cursor bot pushed a commit that referenced this pull request Jan 14, 2026
Allow users to reference Sentry issues by pasting the full issue URL
in addition to the qualified short ID. This supports multiple URL formats:

- https://sentry.io/organizations/{org}/issues/{id}/
- https://{domain}/organizations/{org}/issues/{id}/
- https://sentry.sentry.io/issues/{id}/

The ID can be either a numeric group ID or a qualified short ID (e.g., SENTRY-123).

Previously, users had to use the exact short ID format (e.g., 'Fixes SENTRY-123').
Now they can simply paste the issue URL from their browser, making it easier
to associate PRs and commits with Sentry issues.

Examples that now work:
- 'Fixes https://sentry.io/organizations/sentry/issues/123456/'
- 'n+1 issue\nhttps://sentry.sentry.io/issues/123456/'
- 'https://sentry.io/organizations/org/issues/SENTRY-123/'

Related: #106312

Co-authored-by: josh.ferge <[email protected]>
@scttcper scttcper merged commit 0819d7d into master Jan 15, 2026
68 checks passed
@scttcper scttcper deleted the scttcper/broadcasts-n-1 branch January 15, 2026 00:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants