Skip to content

[pull] master from getsentry:master#1803

Merged
pull[bot] merged 8 commits intoKingDEV95:masterfrom
getsentry:master
Mar 18, 2026
Merged

[pull] master from getsentry:master#1803
pull[bot] merged 8 commits intoKingDEV95:masterfrom
getsentry:master

Conversation

@pull
Copy link
Copy Markdown

@pull pull bot commented Mar 18, 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 : )

priscilawebdev and others added 8 commits March 18, 2026 08:34
…tate layout (#110843)

When the platformized AI agents overview is enabled, the traces table
had a horizontal scrollbar due to hardcoded column widths (the agents
column was fixed at 600px).

This fixes the overflow by:
- Using `COL_WIDTH_UNDEFINED` for the agents column so it fills
available space instead of a fixed 600px
- Removing `fit: max-content` which prevented the table from fitting its
container

Additionally fixes the empty state ("No results") layout where the
message appeared at the top of the widget instead of being vertically
centered:
- `TableWrapper` now uses `flex: 1` to fill remaining vertical space in
the widget card
- `Grid` now sets `grid-template-rows: auto 1fr` when `height` is set
and both `thead`/`tbody` are present, keeping the header compact while
the body fills remaining space



**Before**


https://github.com/user-attachments/assets/2553c168-a69b-406e-8d06-c10fa35e9ede



**After**


https://github.com/user-attachments/assets/f1c88a11-e2a3-4c48-8c1e-c4bdaa09d090



closes
https://linear.app/getsentry/issue/TET-2081/agent-monitoring-dashboard-horizontal-scrollbar-on-table

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Allow DIF assemble to create a second ProjectDebugFile row when a
ProGuard mapping is reuploaded with the same checksum but a different
requested debug ID.

Keep the normal assemble path unchanged for non-ProGuard requests, but
select a ProGuard clone source per checksum and reuse the stored File
when a reupload needs a new debug ID. Skip cached OK results for that
case so the request reaches the clone logic.

Add helper and endpoint coverage for debug ID normalization, ProGuard
clone creation, idempotent reupload, and non-ProGuard error handling.

Supersedes #110442

Fixes #106947
Closes
[INGEST-710](https://linear.app/getsentry/issue/INGEST-710/debug-files-with-identical-content-but-different-debug-ids-rejected-on)
The Select component typings were somehow flawed and turn every prop
into `any`, making quite a mess on each call-side because not a single
prop on select was properly type-checked.

This PR fixes the select type issues, and in turn revealed over 100
issues on usages. I’ve tried to keep most changes type-only, and I’ll
note where we have runtime specific changes in comments.

Most runtime specific changes are about _removing_ props passed to
`Select` that don’t exist and therefore don’t do anything. In many
cases, we passed props that are usually passed to a `FormField` directly
to Select.

For some things I’ve just fallen back to `as any` to not affect
anything, which is an okay trade-off because this PR will make all
future usages of `Select` properly typed.
- Remove SamplingMeasure.TRANSACTIONS enum value and all
transaction-based metric code paths, making SEGMENTS (SpanMRI with
is_segment=true) the sole default measure
- Remove the per-task segment-metric.enabled / segment-metric-orgs
options (8 total) that controlled the gradual TRANSACTIONS → SEGMENTS
migration
- Simplify all 4 dynamic sampling tasks (boost_low_volume_projects,
boost_low_volume_transactions, recalibrate_orgs, sliding_window_org)
from dual SEGMENTS/TRANSACTIONS scanning to a single SEGMENTS pass
-  The SPANS measure (used for AM3/project-mode orgs) is unaffected.
…system (#110298)

Co-authored-by: getsantry[bot] <66042841+getsantry[bot]@users.noreply.github.com>
@pull pull bot locked and limited conversation to collaborators Mar 18, 2026
@pull pull bot added the ⤵️ pull label Mar 18, 2026
@pull pull bot merged commit 356ed75 into KingDEV95:master Mar 18, 2026
@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 Mar 18, 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.

4 participants