-
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
[3.4] avoid closing a watch with ID 0 incorrectly #14562
Conversation
Thanks @kafuu-chino for backporting the PR. Unfortunately, release-3.4 doesn't have integration test at all, so you have to remove the integration test case for now. |
Please try to manually verify this PR indeed fixes the issue, thx |
c6bd21a
to
7fae79b
Compare
In my local test, the token expires and watch can trigger normally. |
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
Thank you @kafuu-chino
@ahrtr @kafuu-chino I think just the path of integration test is different in release-3.4, and we can backport the test case like this? https://github.com/etcd-io/etcd/pull/14548/files#diff-93bc434c49bed544fa4df1bd0750fb22f98c12da81c75f8026520b4eed986108 |
Thanks @mitake for the reminder. release-3.4 indeed has integration test, and paths are as below, |
ok, I'll take a look today. |
Signed-off-by: Kafuu Chino <KafuuChinoQ@gmail.com> add test 1 1 1
7fae79b
to
ed10ca1
Compare
LGTM, thanks @kafuu-chino @ahrtr ! |
Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.
This PR backports #14296 to release-3.4. cc @ahrtr @mitake