-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
ref(proguard): Remove separate queue #74198
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #74198 +/- ##
=======================================
Coverage 78.19% 78.19%
=======================================
Files 6659 6659
Lines 297424 297420 -4
Branches 51184 51183 -1
=======================================
- Hits 232584 232582 -2
+ Misses 58525 58523 -2
Partials 6315 6315
|
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.
🎉 next step, kill the deployment, then profit
Reverting this, the worker first needs to be removed in ops. |
PR reverted: a1ab12d |
This reverts commit 1b13e98. Co-authored-by: loewenheim <[email protected]>
Take two of #74198. The worker was removed in getsentry/ops#11403.
We stopped routing events to the `process_event_proguard` task (and therefore the `events.process_event_proguard` queue) in #74075. The `store.separate-proguard-queue-rate` option was removed from the options automator in getsentry/sentry-options-automator#1895.
This reverts commit 1b13e98. Co-authored-by: loewenheim <[email protected]>
Take two of #74198. The worker was removed in getsentry/ops#11403.
We stopped routing events to the
process_event_proguard
task (and therefore theevents.process_event_proguard
queue) in #74075. Thestore.separate-proguard-queue-rate
option was removed from the options automator in https://github.com/getsentry/sentry-options-automator/pull/1895.