From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: applied: [PATCH manager] ui: ha: status: handle 'fencing' for ordering in grid
Date: Tue, 7 Apr 2026 15:09:40 +0200 [thread overview]
Message-ID: <177556737725.3122671.398282102183521464.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260407102518.57975-1-f.ebner@proxmox.com>
On Tue, 07 Apr 2026 12:24:46 +0200, Fiona Ebner wrote:
> As reported in the community forum [0], the 'fencing' entry might
> bounce around with each API request (with certain browsers, reproduced
> with Chromium 146.0.7680.164). Handle the type 'fencing' when ordering
> to fix this. Order the entry directly after 'quorum', so it can be
> quickly spotted.
>
>
> [...]
Applied, thanks!
[1/1] ui: ha: status: handle 'fencing' for ordering in grid
commit: 7ed516c3ebfd23c69603ce28c8c831cb0f97fa9d
prev parent reply other threads:[~2026-04-07 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 10:24 Fiona Ebner
2026-04-07 11:04 ` Dominik Rusovac
2026-04-07 13:09 ` 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=177556737725.3122671.398282102183521464.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox