From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com, Christoph Heiss <c.heiss@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager] ui: pool: members: fix store reload on add/remove
Date: Tue, 2 Sep 2025 14:32:06 +0200 [thread overview]
Message-ID: <175681632554.470789.16675383817790533858.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250827101430.424606-2-c.heiss@proxmox.com>
On Wed, 27 Aug 2025 12:14:16 +0200, Christoph Heiss wrote:
> .load() must be called on the underlying UpdateStore, not on the
> DiffStore.
>
> Currently, this results in the members list being cleared after
> adding/removing an entry, only being reloaded (correctly) during the
> next automatic background update.
>
> [...]
Applied with bug reference folded in, thanks!
[1/1] ui: pool: members: fix store reload on add/remove
commit: b99d14855f18d956a8eb10fb2f6508e8371790da
Best regards,
--
Fabian Grünbichler <f.gruenbichler@proxmox.com>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-09-02 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 10:14 [pve-devel] " Christoph Heiss
2025-09-02 12:32 ` Fabian Grünbichler [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=175681632554.470789.16675383817790533858.b4-ty@proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=c.heiss@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