-
Notifications
You must be signed in to change notification settings - Fork 0
Replays Self-Serve Bulk Delete System #4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: replays-delete-vulnerable
Are you sure you want to change the base?
Conversation
This validates both the [Working Draft](https://www.w3.org/TR/reporting-1/#concept-reports) and the [Editor's Draft](https://w3c.github.io/reporting/#concept-reports) formats. Fixes [ID-730 - Accept current and upcoming data model](https://linear.app/getsentry/issue/ID-730/accept-current-and-upcoming-data-model).
…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
This adds mode for all things tracing. This encompasses transactions/metrics/spans. Taken from https://github.com/getsentry/sentry/blob/feeaf393deeca8b97675bff23039c6320270aab5/src/sentry/runner/commands/devserver.py#L370
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  after 
### 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.
Co-authored-by: Abdullah Khan <[email protected]>
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.
- getsentry/sentry#93894 removed usage - getsentry/sentry-options-automator#4243 removed the last override
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR appears to be a comprehensive refactoring and feature addition across multiple areas of the Sentry codebase, focusing on test improvements, API enhancements, and UI component updates.
- Refactors test infrastructure for workflow engines and replay handling with better error handling and parameter management
- Adds new table widget visualization components and feedback summary features
- Updates numerous UI components to use standardized Flex layout components instead of custom styled divs
Reviewed Changes
Copilot reviewed 106 out of 106 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| tests/ | Updates test cases for workflow engines, replays, and API endpoints with improved parameter handling and validation |
| static/app/views/ | Major refactoring of UI components to use Flex layout, adds new table widget visualization system |
| static/app/components/ | Replaces custom styled flex containers with standardized Flex components across multiple components |
| src/sentry/workflow_engine/ | Enhances workflow processing with better logging and slow condition handling |
| ErrorEvent, | ||
| get_request_data, | ||
| ) | ||
| from sentry.replays.lib.storage import FilestoreBlob, RecordingSegmentStorageMeta |
Copilot
AI
Jul 26, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nitpick] The import for 'mock_replay' is added but there's no clear indication of its source or purpose. Consider adding documentation or using a more specific import path.
| from sentry.replays.lib.storage import FilestoreBlob, RecordingSegmentStorageMeta | |
| from sentry.replays.lib.storage import FilestoreBlob, RecordingSegmentStorageMeta | |
| # Utility for creating mock replay data in tests |
| def assert_invalid_report_data(self, response: Response, details: dict[str, list[str]]) -> None: | ||
| assert response.status_code == status.HTTP_422_UNPROCESSABLE_ENTITY | ||
| response_data = response.json() # type: ignore[attr-defined] | ||
| assert response_data["error"] == "Invalid report data" | ||
| assert response_data["details"] == details |
Copilot
AI
Jul 26, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nitpick] The helper method 'assert_invalid_report_data' could be made into a reusable test utility function rather than being defined within the test class, improving maintainability across test files.
| def assert_invalid_report_data(self, response: Response, details: dict[str, list[str]]) -> None: | |
| assert response.status_code == status.HTTP_422_UNPROCESSABLE_ENTITY | |
| response_data = response.json() # type: ignore[attr-defined] | |
| assert response_data["error"] == "Invalid report data" | |
| assert response_data["details"] == details | |
| from tests.sentry.utils.test_helpers import assert_invalid_report_data |
Test 5