-
Notifications
You must be signed in to change notification settings - Fork 40.6k
Invalid deprecation information in k8s.io/apimachinery/pkg/util/wait #117829
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
Comments
/sig api-machinery |
/assign @MikeSpreitzer @tkashem |
This issue has not been updated in over 1 year, and should be re-triaged. You can:
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/ /remove-triage accepted |
/triage accepted |
This issue has not been updated in over 1 year, and should be re-triaged. You can:
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/ /remove-triage accepted |
What happened?
The comments for
NewExponentialBackoffManager
read:In particular, the comments are asking us to use
wait.BackoffUntil(..., delayFn.Timer(), ...)
.This does not seem possible, given that the second parameter for
wait.BackoffUntil
is of typeBackoffManager
(interface), whiledelayFn.Timer()
returns aTimer
interface. Maybe the author intended to update the definition ofBackoffUntil
but ended up not doing so for backwards-compatible reasons.Even
wait.BackoffUntil(..., bm.Backoff, ...)
does not seem correct.The documentation for this package needs to be revisited. At the moment, anyone using the latest version of this package would get deprecation warnings from linters, with no remediation possible.
What did you expect to happen?
The documentation should be correct.
How can we reproduce it (as minimally and precisely as possible)?
N/A
Anything else we need to know?
No response
Kubernetes version
K8s v1.27.1, but also master branch
Cloud provider
N/A
OS version
Install tools
Container runtime (CRI) and version (if applicable)
Related plugins (CNI, CSI, ...) and versions (if applicable)
The text was updated successfully, but these errors were encountered: