-
Notifications
You must be signed in to change notification settings - Fork 373
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
[APPSEC-55936] Remove Reactive::Operation #4138
Conversation
2ff17b8
to
332b8fc
Compare
332b8fc
to
d79b926
Compare
BenchmarksBenchmark execution time: 2024-12-11 11:59:45 Comparing candidate commit 220c0a1 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 31 metrics, 2 unstable metrics. |
d79b926
to
5b9ee8b
Compare
5b9ee8b
to
667938d
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #4138 +/- ##
==========================================
+ Coverage 97.75% 97.76% +0.01%
==========================================
Files 1357 1355 -2
Lines 82130 82040 -90
Branches 4174 4171 -3
==========================================
- Hits 80288 80210 -78
+ Misses 1842 1830 -12 ☔ View full report in Codecov by Sentry. |
667938d
to
dfe942e
Compare
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.
I just have one non-blocking suggestion, other than that LGTM!
dfe942e
to
c2f8ac8
Compare
c2f8ac8
to
5e3a4b0
Compare
Hey @Strech this one looks still relevant to merge in at some point? :) |
Datadog ReportBranch report: ✅ 0 Failed, 22063 Passed, 1457 Skipped, 5m 24.89s Total Time |
What does this PR do?
Remove
Reactive::Operation
class as irresponsible proxy.Motivation:
After analysis we decide to move forward without existing reactivity and gateway. Decision made based on the fact that implementation is not finished and subpar on complexity and potentially performance compared to benefits it gives us right now.
Change log entry
No.
Additional Notes:
This is a first step in the direction of simplification of the AppSec instrumentation. To gain some speed we need to trim the deadweight.
How to test the change?
CI is enough.