From: Dominik Csapak <d.csapak@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Rusovac <d.rusovac@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager/proxmox-backup 0/2] fix #7149: ui: prohibit realm update on login
Date: Fri, 19 Dec 2025 09:23:33 +0100 [thread overview]
Message-ID: <887d5b37-55ab-41a3-b17c-dee9c081917f@proxmox.com> (raw)
In-Reply-To: <20251218124210.10483-1-d.rusovac@proxmox.com>
Looks good to me,
consider both patches
Reviewed-by: Dominik Csapak <d.csapak@proxmox.com>
Tested-by: Dominik Csapak <d.csapak@proxmox.com>
On 12/18/25 1:42 PM, Dominik Rusovac wrote:
> The bug relates to PBS, but mentions that the same problem persisted for PVE,
> which I could reproduce.
>
> So, I fixed the bug for both products by the making the realm selection during
> user creation not stateful, after talking to Dominik Csapak (thx btw).
>
>
> proxmox-backup:
>
> Dominik Rusovac (1):
> fix #7149: ui: prohibit realm update on login
>
> www/window/UserEdit.js | 1 +
> 1 file changed, 1 insertion(+)
>
>
> pve-manager:
>
> Dominik Rusovac (1):
> fix #7149: ui: prohibit realm update on login
>
> www/manager6/dc/UserEdit.js | 1 +
> 1 file changed, 1 insertion(+)
>
>
> Summary over all repositories:
> 2 files changed, 2 insertions(+), 0 deletions(-)
>
_______________________________________________
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-12-19 8:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 12:42 Dominik Rusovac
2025-12-18 12:42 ` [pve-devel] [PATCH proxmox-backup 1/1] " Dominik Rusovac
2025-12-18 12:42 ` [pve-devel] [PATCH pve-manager " Dominik Rusovac
2025-12-19 8:23 ` Dominik Csapak [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=887d5b37-55ab-41a3-b17c-dee9c081917f@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=d.rusovac@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.