From: Shan Shaji <s.shaji@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH manager/proxmox{-yew-comp,} v2 0/6] add missing uptime to the GUI, update API dump, and regenerate pve-api-types
Date: Wed, 2 Sep 2026 16:59:38 +0200 [thread overview]
Message-ID: <20260902145944.365185-1-s.shaji@proxmox.com> (raw)
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.
Changes since v1: [1] Thanks @Dominik
- fix white space after "="
- fix idle property always returns 0.
- add idle property to the return schema.
- add uptime to the return schema.
- update API dump and regenerate types.
For the firewall comment format/verify function took reference from the
following patch [2].
- [0] https://man7.org/linux/man-pages/man5/proc_uptime.5.html
- [1] https://lore.proxmox.com/yew-devel/DKYYDNGIAVMV.2WF3ZBQW0OMTW@proxmox.com/T/#t
- [2] https://lore.proxmox.com/pve-devel/20260715093432.34437-1-s.hanreich@proxmox.com/T/#u
pve-manager:
Shan Shaji (2):
fix: nodes: update `idle` key value in hash reference
fix: node: add missing `uptime` property inside the return schema
PVE/API2/Nodes.pm | 12 ++++++++++++
1 file changed, 12 insertions(+)
proxmox-yew-comp:
Shan Shaji (1):
fix #7932: add missing uptime to the GUI
src/node_status_panel.rs | 21 +++++++++++++++++++--
1 file changed, 19 insertions(+), 2 deletions(-)
proxmox:
Shan Shaji (3):
chore: pve-api-types: update API dump and regenerate types
pve-api-types: register missing pve-fw-comment-spec verify function
pve-api-types: update API dump for /node/status and regenerate types
pve-api-types/generate.pl | 2 +-
pve-api-types/pve-api.json | 695 +++++++++++++++++++++------
pve-api-types/src/generated/code.rs | 3 +
pve-api-types/src/generated/types.rs | 36 +-
pve-api-types/src/types/verifiers.rs | 9 +
5 files changed, 584 insertions(+), 161 deletions(-)
Summary over all repositories:
7 files changed, 615 insertions(+), 163 deletions(-)
--
Generated by murpp 0.10.0
next reply other threads:[~2026-09-02 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 14:59 Shan Shaji [this message]
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
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=20260902145944.365185-1-s.shaji@proxmox.com \
--to=s.shaji@proxmox.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.