fix(consumer): call interceptors when MaxProcessingTime expire #1962
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
ghost
added
the
|
mod |
|
@d1egoaz please could you take a look and confirm you're happy with the interceptor changes? |
@dnwe it looks it's doing the right think apparently, something breaks the major loop and not all messages are being intercepted https://github.com/Shopify/sarama/blob/7d06a470f1eeb5d51f48b9a69de7e02f778ecdd6/consumer.go#L470 I'm not too familiar with this block of code but thinks look ok to me |
d1egoaz
approved these changes
Jun 22, 2021
dnwe
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Missing call for interception when MaxProcessingTime timed out and we process the remaining messages