-
Notifications
You must be signed in to change notification settings - Fork 207
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
Remove unexpected event handle message #4388
Merged
Merged
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
Signed-off-by: Krishna Kondaka <[email protected]>
kkondaka
requested review from
chenqi0805,
engechas,
graytaylor0,
dinujoh,
asifsmohammed,
dlvenable and
oeyh
as code owners
April 3, 2024 18:03
dlvenable
previously approved these changes
Apr 3, 2024
graytaylor0
previously approved these changes
Apr 3, 2024
@kkondaka , Should we backport this to 2.7.1? |
Signed-off-by: Krishna Kondaka <[email protected]>
dlvenable
requested changes
Apr 4, 2024
void testDefaultAcknowledgementInvalidRelease() { | ||
defaultAcknowledgementSet.add(event); | ||
defaultAcknowledgementSet.complete(); | ||
DefaultAcknowledgementSet secondAcknowledgementSet = createObjectUnderTest(); | ||
assertThat(defaultAcknowledgementSet.release(handle2, true), equalTo(false)); | ||
assertThat(invalidReleasesCounter, equalTo(1)); |
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.
Should we assert this is equal to 0?
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.
Actually, the counter should be removed.
graytaylor0
approved these changes
Apr 4, 2024
dlvenable
approved these changes
Apr 4, 2024
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.
Description
Remove unexpected event handle message.
This message was added initially because duplicate release was not expected. But with remote peer and aggregate processor support, this can happen now. So, removing the message and the metric.
Issues Resolved
Resolves #[Issue number to be closed when this PR is merged]
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.