From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com, pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH-SERIES] improve warnings handling in UI and add to PVE
Date: Fri, 12 Mar 2021 13:53:23 +0100 [thread overview]
Message-ID: <20210312125329.20918-1-f.ebner@proxmox.com> (raw)
The first half is just a small UI improvement (but it's all over the place),
replacing 'WARNINGS' with (a language-aware) 'Warnings'.
The later half adds the feature of ending in a WARNINGS state to PVE and
provides a usage example.
proxmox-backup and pve-manager need a dependency bump for proxmox-widget toolkit
pve-container needs a dependency bump for pve-common
proxmox-widget-toolkit:
Fabian Ebner (1):
tasks: add warningsText
src/Utils.js | 1 +
src/node/Tasks.js | 3 ++-
2 files changed, 3 insertions(+), 1 deletion(-)
proxmox-backup:
Fabian Ebner (1):
ui: tasks: use warningsText
www/panel/Tasks.js | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
pve-manager:
Fabian Ebner (2):
ui: cluster task log: eslint fixes
ui: cluster task log: handle warnings like the node task log does
www/manager6/dc/Tasks.js | 31 +++++++++++++++++++++----------
1 file changed, 21 insertions(+), 10 deletions(-)
pve-common:
Fabian Ebner (1):
allow workers to count warnings and finish tasks in a WARNINGS state
src/PVE/RESTEnvironment.pm | 20 ++++++++++++++++++--
src/PVE/Tools.pm | 2 ++
2 files changed, 20 insertions(+), 2 deletions(-)
pve-container:
Fabian Ebner (1):
restore: sanitize config: use new warn() function
src/PVE/LXC/Create.pm | 15 +++++++++++----
1 file changed, 11 insertions(+), 4 deletions(-)
--
2.20.1
next reply other threads:[~2021-03-12 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 12:53 Fabian Ebner [this message]
2021-03-12 12:53 ` [pbs-devel] [PATCH widget-toolkit 1/6] tasks: add warningsText Fabian Ebner
2021-03-12 12:53 ` [pbs-devel] [PATCH proxmox-backup 2/6] ui: tasks: use warningsText Fabian Ebner
2021-03-12 12:53 ` [pbs-devel] [PATCH manager 3/6] ui: cluster task log: eslint fixes Fabian Ebner
2021-03-16 13:53 ` [pbs-devel] applied: " Dominik Csapak
2021-03-12 12:53 ` [pbs-devel] [PATCH manager 4/6] ui: cluster task log: handle warnings like the node task log does Fabian Ebner
2021-03-12 12:53 ` [pbs-devel] [PATCH/RFC common 5/6] allow workers to count warnings and finish tasks in a WARNINGS state Fabian Ebner
2021-03-12 12:53 ` [pbs-devel] [PATCH/RFC container 6/6] restore: sanitize config: use new warn() function Fabian Ebner
2021-03-16 14:02 ` [pbs-devel] [PATCH-SERIES] improve warnings handling in UI and add to PVE Dominik Csapak
2021-03-17 8:33 ` Fabian Ebner
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=20210312125329.20918-1-f.ebner@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pbs-devel@lists.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