Skip to content

[pull] master from getsentry:master#2007

Merged
pull[bot] merged 14 commits into
KingDEV95:masterfrom
getsentry:master
May 28, 2026
Merged

[pull] master from getsentry:master#2007
pull[bot] merged 14 commits into
KingDEV95:masterfrom
getsentry:master

Conversation

@pull
Copy link
Copy Markdown

@pull pull Bot commented May 28, 2026

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 : )

chromy and others added 14 commits May 28, 2026 11:17
…ag (#116165)

## Summary

Third in a stack (follow-up to #116162 and #116164). The
`organizations:autofix-on-explorer` flag is now true everywhere, so this
PR removes it.

- Drop the flag registration from `temporary.py`.
- Collapse every `features.has("organizations:autofix-on-explorer",
...)` check to the True branch:
- `search/snuba/backend.py` — always use the
`seer_explorer_autofix_last_triggered` column
- `seer/autofix/issue_summary.py` — always route to
`trigger_autofix_agent`; remove the legacy fallback
- `seer/agent/client_utils.py` — gate only on
`organizations:seer-explorer` (collapse the dual-flag `batch_has` to a
single `features.has`)
- `seer/entrypoints/operator.py` — `trigger_autofix` always calls the
agent path; `trigger_handoff` always fetches via `fetch_run_status`
- Delete the `trigger_autofix_legacy` method on `SeerAutofixOperator`
(no callers remain) and its dead legacy imports.
- Tests: drop the legacy-path tests in `test_operator.py`, rename the
no-longer-distinguished `explorer` tests, and de-flag the remaining
tests.

Net: 9 files changed, 42 insertions, 667 deletions.


Agent transcript:
https://claudescope.sentry.dev/share/XIAoRxeHQ-AT-i3eUi_fVXryk-kKsNjn_0qaxBkUXqE
…16083)

- Sliding window retrieves the total 24h volume from EAP, extrapolates
to the monthly volume, and then gets the sample rate from getsentry's
tier system
- If available, this sample rate is used as the base for project sample
rates for the automatic configurations
- Add the sliding window calculation to the new per-org pipeline
…uration is clear in scheduler (#116367)

just a variable rename, but important for readability, we're going to
query different durations
…ig is enabled (#116371)

- Add an enabled check to the config init to prevent queries from being
run if DS is not enabled for this org
…116375)

Discord App Directory installs were broken: `build_integration` was
rewritten to read state from top-level keys when legacy pipeline views
were removed in #113323, but the surviving
`DiscordExtensionConfigurationView` still bound state under
`state["discord"]`, so users hit `Invalid guild ID. The Discord guild ID
must be entirely numeric.` after authorizing in Discord's App Directory.

This rewires the App Directory entry point through the API pipeline:

- Adds an initial-data serializer accepting `code`, `guild_id`, and
`use_configure`. `OrganizationPipelineEndpoint` binds each validated
field to top-level pipeline state at initialize time.
- Branches `DiscordOAuthApiStep.get_step_data` on `use_configure`: when
set, return `{appDirectoryInstall: True, code, guildId, state}` so the
frontend can advance immediately instead of opening a popup. The
returned `state` is the pipeline's own signature, so `handle_post`'s
existing CSRF check passes unchanged with no conditional.
- `build_integration` reads `use_configure` from top-level state to pick
`configure_url` vs `setup_url` for the OAuth token-exchange
`redirect_uri` parameter (Discord requires that value to byte-exactly
match what was used at authorize).
- Replaces `DiscordExtensionConfigurationView` with a small
`RedirectView` that forwards `/extensions/discord/configure/?...` to
`/extensions/discord/link/?...`. The URL has to keep resolving because
Discord's App Directory listing has it registered as the OAuth
`redirect_uri`; we can't remove it without Discord-side coordination.

Frontend changes (link view triggers the pipeline modal with the URL
params as `initialData`, and the Discord OAuth step component
auto-advances when `appDirectoryInstall` is set) ship in a follow-up PR.
Replaces the previous breakpoint-specific padding on `LayoutGrid` with a
flat `padding: 8px 16px` (`space.md space.xl`) applied at all
breakpoints.

Action taken on behalf of Ryan Albrecht.

**Before**
<img width="1482" height="206" alt="before"
src="https://github.com/user-attachments/assets/47a9eed3-94eb-4a89-ab06-a50258def98f"
/>

**After**
<img width="1482" height="206" alt="after"
src="https://github.com/user-attachments/assets/76d7a7ca-3edd-478f-8e65-f484d46de160"
/>



---
[View Session in
Sentry](https://sentry.sentry.io/traces/?project=4510944073809921&query=gen_ai.conversation.id%3A%22slack%3AC0B63QA6RGA%3A1779975838.713209%22)

---------

Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
Remove relocations code from the typing ignore list and fix up the
typing issues in those modules.
The goal of this PR is to break up the context for the search query
builder into smaller more focused contexts.

Currently the single context is quite large and can probably be narrowed
down for better maintainability of the search query builder.

Closes EXP-963

---------

Co-authored-by: OpenAI Codex <noreply@openai.com>
Snapshot tests launch Chromium via Playwright, render components to
HTML, and capture PNG screenshots. Jest's default 5s test timeout is too
tight for browser automation — especially when multiple workers run in
parallel and compete for CPU/IO — causing spurious timeouts on tests
that are otherwise correct.

Sets `testTimeout: 30_000` in `jest.config.snapshots.ts` to match
Playwright Test's own default for browser-driven tests. This only
affects snapshot tests; the main Jest config is unchanged.
streamlined issue details has been GA for a while now, so this moves the
old streamline implementation into the regular issueDetails area and
drops the v2 style naming from folders, components, etc.
@pull pull Bot locked and limited conversation to collaborators May 28, 2026
@pull pull Bot added the ⤵️ pull label May 28, 2026
@pull pull Bot merged commit 887ccc9 into KingDEV95:master May 28, 2026
0 of 2 checks passed
@github-actions github-actions Bot added Scope: Frontend Automatically applied to PRs that change frontend components Scope: Backend Automatically applied to PRs that change backend components labels May 28, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

⤵️ pull Scope: Backend Automatically applied to PRs that change backend components Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.