From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Shan Shaji <s.shaji@proxmox.com>
Subject: applied: [PATCH manager/proxmox{-yew-comp,} v2 0/6] add missing uptime to the GUI, update API dump, and regenerate pve-api-types
Date: Fri, 16 Oct 2026 01:21:13 +0200 [thread overview]
Message-ID: <179210637531.3746002.4110914613482426474.b4-ty@b4> (raw)
In-Reply-To: <20260902145944.365185-1-s.shaji@proxmox.com>
On Wed, 02 Sep 2026 16:59:38 +0200, Shan Shaji wrote:
> This series adds missing uptime [0] to the GUI. I have also updated the API
> dump and regenerated the types after adding the missing idle and
> uptime properties to the return schema of Proxmox VE's /nodes/{node}/status
> endpoint. This also fixes an issue where the idle field always returned 0.
>
> Apart from patch [3/6], all other patches are new.
>
> [...]
Applied, thanks!
[pve-manager] applied to pve-manager.git (master)
[1/6] fix: nodes: update `idle` key value in hash reference
https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=cab6365b12f4a6b518c5de3a8a64ca4cda7be3d3
[2/6] fix: node: add missing `uptime` property inside the return schema
https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=8a90e37cdb921d26eab1117fbd5f2597f3e2f6ec
[proxmox] applied to git/proxmox.git (master)
[4/6] chore: pve-api-types: update API dump and regenerate types
commit: e50e7cb6d8302e720de66175c9a0993a0656d908
[5/6] pve-api-types: register missing pve-fw-comment-spec verify function
commit: 7476d39c88ed3d8134c47118336b9d4929c1f00b
[6/6] pve-api-types: update API dump for /node/status and regenerate types
commit: 2d3ec24a5b8c0cafb1f14e03715e967f6cc352b3
[proxmox-yew-comp] applied to ui/proxmox-yew-comp (master)
[3/6] fix #7932: add missing uptime to the GUI
commit: 1fa20cdf90c589397fe26cd23fe981547f94d1a1
prev parent reply other threads:[~2026-10-15 23:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 14:59 [PATCH manager/proxmox{-yew-comp,} v2 0/6] add missing uptime to the GUI, update API dump, and regenerate pve-api-types Shan Shaji
2026-09-02 14:59 ` [PATCH pve-manager v2 1/6] fix: nodes: update `idle` key value in hash reference Shan Shaji
2026-09-02 14:59 ` [PATCH pve-manager v2 2/6] fix: node: add missing `uptime` property inside the return schema Shan Shaji
2026-09-02 14:59 ` [PATCH proxmox-yew-comp v2 3/6] fix #7932: add missing uptime to the GUI Shan Shaji
2026-09-02 14:59 ` [PATCH proxmox v2 4/6] chore: pve-api-types: update API dump and regenerate types Shan Shaji
2026-09-02 14:59 ` [PATCH proxmox v2 5/6] pve-api-types: register missing pve-fw-comment-spec verify function Shan Shaji
2026-09-02 14:59 ` [PATCH proxmox v2 6/6] pve-api-types: update API dump for /node/status and regenerate types Shan Shaji
2026-10-15 23:21 ` 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=179210637531.3746002.4110914613482426474.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.shaji@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox