-
Notifications
You must be signed in to change notification settings - Fork 110
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
Retry offset commit #3103
Retry offset commit #3103
Conversation
Before this patch, we were caching the new offset before committing to Kafka the offset, causing the offset to not be stored until a new record is successfully processed. Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
Codecov Report
@@ Coverage Diff @@
## main #3103 +/- ##
============================================
- Coverage 63.38% 63.36% -0.03%
- Complexity 757 758 +1
============================================
Files 167 167
Lines 11353 11354 +1
Branches 232 233 +1
============================================
- Hits 7196 7194 -2
- Misses 3633 3635 +2
- Partials 524 525 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: matzew, pierDipi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
78727d7
into
knative-extensions:main
/cherry-pick release-1.10 |
/cherry-pick release-1.9 |
@pierDipi: new pull request created: #3104 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@pierDipi: new pull request created: #3105 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Before this patch, we were caching the new offset before committing to Kafka the offset, causing the offset to not be stored until a new record is successfully processed. Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
Before this patch, we were caching the new offset before committing to Kafka the offset, causing the offset to not be stored until a new record is successfully processed. Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com> Co-authored-by: Pierangelo Di Pilato <pierdipi@redhat.com>
Before this patch, we were caching the new offset before committing to Kafka the offset, causing the offset to not be stored until a new record is successfully processed.