Skip to content

Conversation

@akshayutture-augment
Copy link

@akshayutture-augment akshayutture-augment commented Nov 14, 2025

Test 5


Replicated from ai-code-review-evaluation/sentry-cursor#5


Note

Adds a new dashboards table visualization and refactors Explore visualize model to a single yAxis, enhances replay/feedback AI, hardens browser reporting, updates PR comment formatting, workflows, and various UI/infra configs.

  • Frontend:
    • Dashboards: Introduces TableWidgetVisualization with default cell renderers, stories, fixtures, and tests; new Tabular* types.
    • Explore: Refactors Visualize to single yAxis (API, toolbar, analytics, sorting, add-to-dashboard, aggregates editor); adds hooks for trace item attribute keys/values; updates logs/metrics handling.
    • Feedback: Adds AI feedback summary component/hook and integrates into list page.
    • Replays: Adds timeline zoom analytics, renames view-html event, improves AI tab project lookup/error handling.
    • UI: Replaces ad‑hoc flex containers with Flex; minor style/transition tweaks.
  • Backend:
    • Replays: Replay summarize endpoint now merges error events into logs; bulk delete tolerates null max_segment_id.
    • Browser Reporting: Rewrites collector with DRF serializer/validation and proper HTTP statuses; expands tests.
    • PR Comment Bots: New merged PR issue format with truncated titles and environment info (GitHub/GitLab); helpers in commit context.
    • Workflow Engine: Precomputes/passes slow conditions, improves logging; detectors support owner (user/team) on create/update.
    • Tasks/Infra: Adds processing_deadline_duration to taskworkers; adds snuba-metrics service and tracing mode in devservices.
    • Defaults/Options: Changes autofix default to off; removes regex parameterization experiments/option; adds noise config for DB query injection; adds preprod analytics event and records it in API.
  • Migrations/Tests:
    • Marks older saved search conversions as no-op; broad test updates including logs Top-N and browser reporting.

Written by Cursor Bugbot for commit ea188e2. Configure here.

armenzg and others added 30 commits June 20, 2025 12:49
…o 'low' (#93927)"

This reverts commit 8d04522.

Co-authored-by: roaga <[email protected]>
Missed in the initial commit, leading to some relevant logs being
unannotated.
We have had a few tasks get killed at 10% rollout.
Also add a test, so that this doesn't happen again
Fixes DE-129 and DE-156

---------

Co-authored-by: Cursor Agent <[email protected]>
These transitions should be matching
…` (#93946)

Use `project_id` on the replay record instead of the URL (where it does
not always exist).

---------

Co-authored-by: Cursor Agent <[email protected]>
Co-authored-by: getsantry[bot] <66042841+getsantry[bot]@users.noreply.github.com>
Also fixed `replay.view_html` -> `replay.view-html`

---------

Co-authored-by: Michelle Zhang <[email protected]>
…948)

gets `npx @typescript/native-preview` passing again
The conditions associated with a DCG can change over time, and it's good
if we can be completely confident that they're consistent within a given
task execution.
This is unused and most regex experiments have required broader changes
to ensure that regexes are evaluated in a specific order (ex:
traceparent). Removing this for now to simplify the code and very
slightly improve runtime performance.
From some testing (on feedback lists of all different lengths), this
prompt seems to work better. It doesn't write overly long sentences and
also does a better job at "summarizing" versus just mentioning a few
specific topics and leaving out others.
Just remove a couple custom Flex* classes in favor of the Flex primitive
This has been killed a few times.

Refs SENTRY-42M7
…n table (#93892)

<!-- Describe your PR here. -->

[ticket](https://linear.app/getsentry/issue/ID-156/grouping-info-remove-type-field-from-ui)
The Type field in the Grouping Info section of the issue details page
was redundant.
This removes the Type row from all variant types while keeping the
underlying data structure intact.

before
![Screenshot 2025-06-20 at 12 00
54 PM](https://github.com/user-attachments/assets/97ca72da-0a52-4446-9825-cd4fcb505adf)

after
![Screenshot 2025-06-20 at 11 59
29 AM](https://github.com/user-attachments/assets/a4284d2b-c9f5-442f-b010-7fe72a598e39)
### Changes
Related to this PR: getsentry/sentry#93810. This
is part 1 of the change, which is pulling out the new component and just
adding it to the repo. Also includes some simplification of the logic in
the base component.

Part 2 will be replacing tables in widgets.

### Before/After

There is no UI change as the table is not being used yet. There is a new
story page for the component.
…93943)

to prevent this issue from becoming too noisy, add a noise config
Unfortunately, 'event_data' went from being the variable for current
event context to being the complete parsed data from Redis, and we
continued logging it per group.
That's more data than we should be logging even arguably once, let alone
per group.
Adds some simple analytics to our endpoint so we can begin building a
dashboard in Amplitude.
Previously, explore supported multiple y axis per chart, so each
visualize supported multiple y axis. That functionality has since been
removed for simplicity so update the types here to match. Keep in mind
that saved queries still store them as an array so when
serializing/deserializing, we still need to treat it as an array.
We'll need the `useGetTraceItemAttributeKeys` hook in other places so
refactoring it so that it can exported.
mrduncan and others added 2 commits June 20, 2025 13:20
When the max segment ID is null the process fails. We should exit early
since if there aren't any segments to delete there's nothing to do.
@akshayutture-augment
Copy link
Author

cursor review

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

✅ Bugbot reviewed your changes and found no bugs!


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.