-
Notifications
You must be signed in to change notification settings - Fork 2.9k
vendor: bump c/common to 9b0d134f392
#25753
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
Conversation
Bump common to 9b0d134f392f41de3f3065aad162e73a3904168e Signed-off-by: flouthoc <[email protected]>
|
Followup PR after containers/common#2401 |
mtrmac
left a comment
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 but lint is unhappy.
SA1019: types.RegexError is deprecated: use [ErrInvalidName] instead. Making linter happy. Signed-off-by: flouthoc <[email protected]>
| NameRegex = types.NameRegex | ||
| // RegexError is thrown in presence of an invalid container/pod name. | ||
| RegexError = types.RegexError | ||
| RegexError = types.ErrInvalidName |
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.
This works, but maybe the variable could also be renamed.
… does Podman promise a stable API for this package?
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.
no, we can break that.
The remote client cannot keep type information across the wire anyway so it would be pointless for anyway to try to errors.Is() that in their go client code.
Luap99
left a comment
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
In the interest of fixing the breaking vendor change, we can consider changing the error name in podman later.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: flouthoc, Luap99 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
4b24725
into
containers:main
Bump common to 9b0d134f392f41de3f3065aad162e73a3904168e
Does this PR introduce a user-facing change?