Skip to content
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.

Sign up for GitHub

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

Jump to bottom

informer isWatching returns false, when it is watching #3484

Closed
shawkins opened this issue Sep 21, 2021 · 0 comments · Fixed by #3485
Closed

informer isWatching returns false, when it is watching #3484

shawkins opened this issue Sep 21, 2021 · 0 comments · Fixed by #3485
Labels
bug
Milestone
5.8.0

Comments

@shawkins
Copy link
Contributor

It appears that both onClose methods are being called which results in the Reflector/Informer logic interprets the second call as watching = false
@shawkins shawkins added this to the 5.8.0 milestone Sep 21, 2021
@shawkins shawkins mentioned this issue Sep 21, 2021
Closed
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Sep 21, 2021
@shawkins
fix fabric8io#3484: ensuring that only one close method is called suc…
023b3b3 
…cessfully
@shawkins shawkins mentioned this issue Sep 21, 2021
Merged
11 tasks
@manusa manusa added the bug label Sep 21, 2021
@manusa manusa linked a pull request Sep 22, 2021 that will close this issue
fix #3484: ensuring that only one close method is called successfully #3485
Merged
11 tasks
manusa pushed a commit to shawkins/kubernetes-client that referenced this issue Sep 22, 2021
@shawkins @manusa
fix fabric8io#3484: ensuring that only one close method is called suc…
a9366ef 
…cessfully
manusa pushed a commit that referenced this issue Sep 22, 2021
@shawkins @manusa
fix #3484: ensuring that only one close method is called successfully
9e8ae39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
5.8.0
Development

Successfully merging a pull request may close this issue.

fix #3484: ensuring that only one close method is called successfully shawkins/kubernetes-client
2 participants
@manusa @shawkins