[pull] master from getsentry:master#1846
Merged
Merged
Conversation
Get some more visibility into what is happening within outbox backfill machinery.
I'm mainly adding UI to start, so I've added the page filters and search bar but they don't work yet! This is what it looks like <img width="1432" height="473" alt="image" src="https://github.com/user-attachments/assets/851846c7-206b-49b7-a765-3129c5d082e8" />
Register the `organizations:ourlogs-table-expando` feature flag to gate the expand/collapse table height toggle in the logs UI. Split out from #109819 so the flag lands independently of the UI changes. Made with [Cursor](https://cursor.com) Co-authored-by: Claude Opus <noreply@anthropic.com>
We have incrementally patched a few problematic associations. This change should solve those problems generally by using schema reflection and generating query conditions dynamically based on relationship trees. Refs SENTRY-5HVP
Currently we use `import * as Stories from 'sentry/stories'` in quite a few places. When working on #111369, I discovered that this can cause circular imports in the `Button` component because `APIReference` and `ThemeSwitcher` imported `Button` internally. This PR cleans up the `sentry/stories` barrel file to remove circular import opportunities
Supports typescript v6, fix some reasonable new lint errors
This PR re-implements the `slack` integration and all its capabilities as a `slack-staging` provider to allow for testing a staging application in production. Details for this [in this doc](https://www.notion.so/sentry/Supporting-a-Staging-Slack-App-32d8b10e4b5d8074a921c2b854e53cf0?source=copy_link). Currently tested: - Alerts - Personal notifications - Notification platform (new) - Installation/uninstallation - Webhooks, slash commands https://linear.app/getsentry/issue/ISWF-2299/prototype-the-separate-staging-provider-slack-app --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
…PR comments (#112100) Register the infrastructure needed to gate snapshot PR comments: - Feature flag: `organizations:preprod-snapshot-pr-comments` (FlagPole, api_expose=True) - Project option: `sentry:preprod_snapshot_pr_comments_enabled` (default true) - Serializer field and PUT handler in project details endpoint so the toggle is read/writable via the API This is the first step toward EME-999 — adding PR comment support for snapshot comparisons. Follow-up PRs will add the task, template, frontend toggle, and trigger wiring. Refs EME-999 --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
pass an objectstore token to symbolicator alongside minidump/applecrashreport attachment URLs NOTE: token expiry time is set in the global client and shared across usecases/sessions. the default value is 60s.
Previously, we only used an option to decide whether the extended slack scopes should be used or not. This had a couple of problems: - No org-level control. If one org wants to try out extended scopes, all of Sentry would need to enable extended scopes which leads to: - Extra scope requested for the not-updated prod Slack app. If we request more scope than required in the production Slack app, then Slack will return an error, saying extra scope was requested. Now that we have a SlackStagingIntegrationProvider, we can assume we already have the appropriate scopes in the Staging app, and use the extended scopes for all Staging app installations.
github-actions
Bot
added
Scope: Frontend
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
12 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )