From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Lucas Barros <lucasbarros.kam@gmail.com>
Subject: applied: [PATCH container] fix #8162: status: always return 'cpus' as number
Date: Sat, 14 Nov 2026 22:33:01 +0100 [thread overview]
Message-ID: <179469198023.2480055.7001419132572421409.b4-ty@b4> (raw)
In-Reply-To: <20261107221120.13176-1-lucasbarros.kam@gmail.com>
On Sat, 07 Nov 2026 19:11:20 -0300, Lucas Barros wrote:
> For containers that only have 'cpulimit' set, the 'cpus' property of
> the status API endpoints was encoded as a JSON string, for example
> "cpus":"2", while the API schema declares it as a number. Clients that
> decode the response strictly by the schema, like the Terraform
> provider for Proxmox VE, fail to parse it.
>
> The config parser keeps values of 'number' typed options like
> 'cpulimit' as string, while 'integer' options like 'cores' are
> converted with int(). Explicitly convert the value to a number, so
> 'cpus' has the same type regardless of which option it comes from.
>
> [...]
Applied, thanks!
[1/1] fix #8162: status: always return 'cpus' as number
commit: a07edd2eda940504132f9300de6b730635e6a5ff
prev parent reply other threads:[~2026-11-14 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 22:11 [PATCH container] fix #8162: status: always return 'cpus' as number Lucas Barros
2026-11-14 21:33 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=179469198023.2480055.7001419132572421409.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=lucasbarros.kam@gmail.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.