Skip to content

Conversation

@markstory
Copy link
Member

We render the bulk of our HTML via ReactPage. Right now that endpoint is marked as all_silo to make integration with tests simpler. Switch these endpoints to control as we're trying to have a minimal number of endpoints marked as all_silo and I want to better understand the scope of test failures from this change.

Refs INFRENG-238

We render the bulk of our HTML via ReactPage. Right now that endpoint is
marked as `all_silo` to make integration with tests simpler. Switch
these endpoints to control as we're trying to have a minimal number of
endpoints marked as `all_silo` and I want to better understand the scope
of test failures from this change.

Refs INFRENG-238
@linear
Copy link

linear bot commented Dec 8, 2025

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Dec 8, 2025
@codecov
Copy link

codecov bot commented Dec 8, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #104552      +/-   ##
===========================================
+ Coverage   80.52%    80.54%   +0.02%     
===========================================
  Files        9352      9354       +2     
  Lines      400460    400945     +485     
  Branches    25696     25696              
===========================================
+ Hits       322477    322952     +475     
- Misses      77533     77543      +10     
  Partials      450       450              

- Change silo mode of UI endpoint tests to be control scoped as
  ReactPage is now control scoped.
- Update a route name to not overlap with the non-customer domain path.
Subclasses of `sentry.web.frontend.base.BaseView` should not be part of
the controlsilo URL map because the UI will not make requests to these
paths.
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Dec 9, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 9, 2025

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

r"^(?P<organization_slug>[^/]+)/projects/(?P<project_id_or_slug>[^/]+)/events/(?P<client_event_id>[^/]+)/$",
ProjectEventRedirect.as_view(),
name="sentry-project-event-redirect",
name="sentry-organization-project-event-redirect",
Copy link
Member Author

Choose a reason for hiding this comment

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

We had two routes with this name 🫠

markstory added a commit that referenced this pull request Dec 10, 2025
In #104552 I want to make `ReactPage` control-only. This change
*should* be a no-op for saas, but I want to make sure of that first by
validating with real traffic.

Refs INFRENG-238
markstory added a commit that referenced this pull request Dec 10, 2025
In #104552 I want to make `ReactPage` control-only. This change *should*
be a no-op for saas, but I want to make sure of that first by validating
with real traffic.

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

Labels

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.

3 participants