-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
kubeadm: prefer to use pkg/errors package and cleanup fmt.Errorf #111394
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: SataQiu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should just use the pkg/errors package and Wrap(f) instead. despite deprecated the library gives us the consistent wrapping that we need. stdlib and %w dont have that.
we might actually fork it at some point.
/hold |
Emm... On second check, we do use |
yes. in fact we had an effort to clean all usage of fmt.Errorf. (that was when we started using pkg/errors) |
90994af
to
7ce2874
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
thanks
/hold cancel |
7ce2874
to
6cab980
Compare
Thanks @neolit123 Need LGTM again |
/lgtm |
/retest |
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
[kubeadm: prefer to use pkg/errors package and cleanup fmt.Errorf]
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: