Closed CiprianAnton closed 6 months ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
any ideas @alexzielenski @howardjohn @lavalamp @liggitt @dims @pohly ?
/remove-lifecycle stale
/reopen
@tooptoop4: You can't reopen an issue/PR unless you authored it or you are a collaborator.
This issue is the root cause for https://github.com/argoproj/argo-workflows/issues/10947
Based on my tests, the issue was introduced between client-go
v0.24.0-alpha.1
andv0.24.0-alpha.2
.Seems like when the first resync happens (20 minutes in case of argo-workflows), the event handlers are not being called.
I was able to identify a potential change that introduced this: https://github.com/kubernetes/client-go/commit/54928eef9f824667b23a938188498992d437156a#diff-dbac68d65bbc9814c2336df6ee91f22e807d84a9127a4d34a8b39c5657d0e447L551
Looking at the code, there is small behavior change when evaluating the isSync flag:
d.Type == Replaced
. Now it's being evaluated on all updatesd.Type == Sync
set the isSync to trueAll an in one, there might be a chance of falsely setting isSync to true.
This flag is being used in
distribute
, which conditionally calls the listeners.The issue also reproduces with latest client-go version: v0.29.0-alpha.2