-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Add ulimits to podman update
#26445
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
base: main
Are you sure you want to change the base?
Add ulimits to podman update
#26445
Conversation
|
[NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore. |
2 similar comments
|
[NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore. |
|
[NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore. |
|
Hi, I did a quick code check. And you need to move this definition of the |
|
The commit needs a sign off, see https://github.com/containers/podman/blob/main/CONTRIBUTING.md#sign-your-prs Also please add the |
22d4ec1 to
81fe400
Compare
|
What is the merge workflow for this project? Should I always squash my commits into a single commit? |
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.
Does this work correctly with --ulimit host on update? AFAICT it should unset all limts from the spec but the parser sets it to nil which means the update code considers it unset? I think the code likely needs to pass an explicit empty slice in that case?
For a small feature like this yes. In general commits must be logical units and we prefer code, test and docs to be part of the same commit. However if you do some slight refactoring or fix multiple things than they should be in separate commits. |
e03b8f4 to
32aa965
Compare
32aa965 to
beda41d
Compare
ccc007e to
512efe2
Compare
4daaf4b to
cf33218
Compare
63f34be to
6735519
Compare
Honny1
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.
The linter is failing. Please rebase to main to ensure the recent linter updates are applied to your changes.
b8c16a5 to
e016879
Compare
|
@Honny1 seems like the failures are unrelated? |
|
Yes, it looks like that. I reran the tests. |
|
|
||
| if err := decoder.Decode(&query, r.URL.Query()); err != nil { | ||
| utils.Error(w, http.StatusBadRequest, fmt.Errorf("failed to parse parameters for %s: %w", r.URL.String(), err)) | ||
| utils.BadRequest(w, "restartPolicy", query.RestartPolicy, err) |
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.
I’m not sure about this. At first glance it makes sense, but looking deeper, I am not sure about the query.RestartPolicy value. Will it be an empty string when parsing fails, or something else?
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.
good point, I've reverted the changes.
Signed-off-by: Aaron Ang <[email protected]>
Signed-off-by: Aaron Ang <[email protected]>
e016879 to
a9dd858
Compare
Honny1
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.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aaron-ang, Honny1 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 |
Fixes: #26381
Does this PR introduce a user-facing change?