You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A test began failing after a Kube-RS upgrade from 0.91 to 0.93 - rough sketch:
let _ = api.delete(&obj).await;
// never returns now as there is no object at the point of awaiting
await_condition(self.api.clone(), obj.name_unchecked(), conditions::is_deleted).await;
Looking at the earlier implementation an Ok(None) event would be passed up to check when no objects were returned. -
Use "scan" to track whether or not the object was seen for each round of Init events. If the object was seen InitDone will return None otherwise it should pass Ok(None).
Additional context
No response
Environment
N/A
Configuration and features
No response
Affected crates
kube-runtime
Would you like to work on fixing this bug?
yes
The text was updated successfully, but these errors were encountered:
Current and expected behavior
A test began failing after a Kube-RS upgrade from 0.91 to 0.93 - rough sketch:
Looking at the earlier implementation an
Ok(None)
event would be passed up to check when no objects were returned. -kube/kube-runtime/src/watcher.rs
Line 815 in 5dbae3a
After 0.92 the "InitDone" always leads to
None
-kube/kube-runtime/src/watcher.rs
Line 830 in 0f6cb6f
Possible solution
Use "scan" to track whether or not the object was seen for each round of
Init
events. If the object was seenInitDone
will returnNone
otherwise it should passOk(None)
.Additional context
No response
Environment
N/A
Configuration and features
No response
Affected crates
kube-runtime
Would you like to work on fixing this bug?
yes
The text was updated successfully, but these errors were encountered: