-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
feat(mep): fix header filter error #2938
Conversation
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.
Why wasn't this caught with an existing test?
If you look at the original PR #2929, it felt more like a config than a functionality change. Any test would basically be mimicking the tests in |
Co-authored-by: Lyn Nagara <[email protected]>
Still regarding the test. Did we already create the end to end test for this dataset? That should have caught it |
Codecov Report
@@ Coverage Diff @@
## master #2938 +/- ##
==========================================
- Coverage 92.93% 92.87% -0.06%
==========================================
Files 635 635
Lines 29069 29081 +12
==========================================
- Hits 27016 27010 -6
- Misses 2053 2071 +18
Continue to review full report at Codecov.
|
The way we write e2e tests (at least since I've joined) directly invokes so we can't apply a header-based pre-filter with this mechanism. To do that I think we'd need to build an actual consumer /processing strategy factory (e.g. https://github.com/getsentry/snuba/blob/master/snuba/consumers/consumer_builder.py#L221-L265) |
I mistakenly thought that the
KafkaHeaderFilter
was passing matches but it was actually dropping them, so we were dropping all MEP messages (which is fine, it's pre-prod).This fixes the issue