Update consumer flags #3112
Merged
Update consumer flags #3112
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
azaslavsky
approved these changes
Jun 4, 2024
lynnagara
approved these changes
Jun 4, 2024
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #3112 +/- ##
==========================================
- Coverage 99.01% 94.08% -4.93%
==========================================
Files 3 3
Lines 203 203
==========================================
- Hits 201 191 -10
- Misses 2 12 +10 ☔ View full report in Codecov by Sentry. |
jamesbaber1
pushed a commit
to Algo-Trading-Tools/sentry
that referenced
this pull request
Jun 20, 2024
update consumer flags
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
talked to @lynnagara, ingest consumers are not run with
--no-strict-offset-reset, but post process forwarders areThis should fix #2951