From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pbs-devel@lists.proxmox.com,
Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
Subject: applied: [PATCH proxmox-backup v3] ui: encryption keys: show error text instead of empty popup in API alerts
Date: Wed, 29 Apr 2026 18:23:49 +0200 [thread overview]
Message-ID: <177747982920.3682415.12893129435094764976.b4-ty@b4> (raw)
In-Reply-To: <20260429101139.163532-1-a.bied-charreton@proxmox.com>
On Wed, 29 Apr 2026 12:11:06 +0200, Arthur Bied-Charreton wrote:
> The errors returned by the encryption-keys and tape-encryption-keys
> endpoints are not plain strings, so the alerts displayed on API2 errors
> like failed permission checks end up being empty and therefore not very
> helpful.
>
> Extract the error messages to display them correctly in alerts.
>
> [...]
Applied, thanks!
[1/1] ui: encryption keys: show error text instead of empty popup in API alerts
commit: e685a30c3e2c071116b21d43e13726f9cd1a8d5d
prev parent reply other threads:[~2026-04-29 16:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 10:11 [PATCH proxmox-backup v3] ui: encryption keys: show error text instead of empty popup in API alerts Arthur Bied-Charreton
2026-04-29 16:23 ` 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=177747982920.3682415.12893129435094764976.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=a.bied-charreton@proxmox.com \
--cc=pbs-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