-
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
receipt: dequeue not returning watch err #17198
base: main
Are you sure you want to change the base?
Conversation
Hi @wxsms. Thanks for your PR. I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
Can you add a test? |
Hi there, Thanks for reply, I just added a test to simulate an error during watch by shutting down a cluster, since I'm very new to etcd, not sure if I make it correctly. The main propose of this PR is to make sure watch return a non-nil value or error. The testcase will failed as followed if queue code stay untouched:
|
the error from watch is not returned, if the client token expired, the `ev` return by watch will be nil, therefore the Deque method will panic in such case. Signed-off-by: guokairui <wxsms@foxmail.com>
Signed-off-by: guokairui <wxsms@foxmail.com>
/retest |
/retest |
cc @moficodes |
/retest |
the error from watch is not returned, if the client token expired, the
ev
return by watch will be nil, therefore the Deque method will panic in such case.Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.