-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
[release-3.5] backport fix watch event loss after compaction #17612
[release-3.5] backport fix watch event loss after compaction #17612
Conversation
Signed-off-by: Chao Chen <[email protected]>
Thanks for the PR. I do not see the integration test case, did you intentionally not backporting the integration test? |
Yeah, go failpoint in the mainline integration test is not supported in release-3.5. I can create one similar e2e test just like TestLeaseRevoke_IgnoreOldLeader though. |
Thanks for the clarification. I am OK to leave it as it's for now. |
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.
Please also update the changelog for 3.4 and 3.5, thx |
Thanks @ahrtr for releasing v3.4.31! Is there a ETA for releasing [v3.5.13] including the bug fix so we can count on? @serathius |
Created planning issue #17633 to start the process. |
Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.
xref. #17529