-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
informOnCondition should not test initial add events #4082
Milestone
Comments
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Apr 21, 2022
also improving informOnCondition
11 tasks
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Apr 21, 2022
also improving informOnCondition
I think this only started to be an issue after supporting batching #3587 - before once a list was obtained it was set on the store as a single replace operation. |
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Apr 21, 2022
also improving informOnCondition
manusa
pushed a commit
to shawkins/kubernetes-client
that referenced
this issue
Apr 28, 2022
also improving informOnCondition
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your enhancement related to a problem? Please describe
If you are using informOnCondition to check for non-existence the initial add events will provide a partial list and therefore potentially a misleading state.
Describe the solution you'd like
Test the state initially based upon the full list.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: