-
Notifications
You must be signed in to change notification settings - Fork 181
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
config: add omitzero for numeric types #795
Conversation
@baude @ashley-cui @mheon @rhatdan @vrothberg PTAL |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Luap99, vrothberg 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 |
When toml writes the config file it does not use `omitempty` for numeric values instead it requires `omitzero`. [1] The problem is that without this change, `config.Write()` writes ``` [machine] cpus = 0 disk_size = 0 memory = 0 ``` to the user file. Because podman machine system connection add code will do this the config file is broken afterwards. The first vm will be created successfully but after this every other vm will be broken because the cpu, memory and disk size are set to zero. [1] BurntSushi/toml#81 Fixes containers/podman#11824 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
I just added a test to prevent regressions. |
LGTM, good catch, thanks!! |
/lgtm Ack on backport to 3.4, guess we need to start planning a 3.4.1. |
/hold cancel |
When toml writes the config file it does not use
omitempty
for numericvalues instead it requires
omitzero
. [1]The problem is that without this change,
config.Write()
writesto the user file. Because podman machine system connection add code will
do this the config file is broken afterwards. The first vm will be created
successfully but after this every other vm will be broken because the
cpu, memory and disk size are set to zero.
[1] BurntSushi/toml#81
Fixes containers/podman#11824