public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com, pbs-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH-SERIES v2] improve warnings handling in UI and add to PVE
Date: Fri,  9 Apr 2021 10:44:29 +0200	[thread overview]
Message-ID: <20210409084436.2454-1-f.ebner@proxmox.com> (raw)

Changes from v1:
    * dropped already applied patches
    * add format_task_status helper and use that everywhere
    * improve usage of replace() (for the widget-toolkit change)
    * chomp the message in warn() (for the pve-common change)


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


widget-toolkit:

Fabian Ebner (3):
  task status: create helper for formatting
  format task status: rename variable
  format task status: improve replace() usage

 src/Utils.js      | 11 +++++++++++
 src/node/Tasks.js | 10 +---------
 2 files changed, 12 insertions(+), 9 deletions(-)


proxmox-backup:

Fabian Ebner (1):
  ui: tasks: use format_task_status

 www/panel/Tasks.js | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)


manager:

Fabian Ebner (1):
  ui: cluster task log: handle warnings like the node task log does

 www/manager6/dc/Tasks.js | 17 ++++++++++-------
 1 file changed, 10 insertions(+), 7 deletions(-)


common:

Fabian Ebner (1):
  allow workers to count warnings and finish tasks in a WARNINGS state

 src/PVE/RESTEnvironment.pm | 22 ++++++++++++++++++++--
 src/PVE/Tools.pm           |  2 ++
 2 files changed, 22 insertions(+), 2 deletions(-)


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





             reply	other threads:[~2021-04-09  8:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09  8:44 Fabian Ebner [this message]
2021-04-09  8:44 ` [pve-devel] [PATCH v2 widget-toolkit 1/7] task status: create helper for formatting Fabian Ebner
2021-04-23 12:54   ` [pve-devel] applied: " Thomas Lamprecht
2021-04-09  8:44 ` [pve-devel] [PATCH v2 widget-toolkit 2/7] format task status: rename variable Fabian Ebner
2021-04-23 12:54   ` [pve-devel] applied: " Thomas Lamprecht
2021-04-09  8:44 ` [pve-devel] [PATCH v2 widget-toolkit 3/7] format task status: improve replace() usage Fabian Ebner
2021-04-23 12:54   ` [pve-devel] applied: " Thomas Lamprecht
2021-04-09  8:44 ` [pve-devel] [PATCH v2 proxmox-backup 4/7] ui: tasks: use format_task_status Fabian Ebner
2021-04-09  8:44 ` [pve-devel] [PATCH v2 manager 5/7] ui: cluster task log: handle warnings like the node task log does Fabian Ebner
2021-04-09  8:44 ` [pve-devel] [PATCH/RFC v2 common 6/7] allow workers to count warnings and finish tasks in a WARNINGS state Fabian Ebner
2021-04-23 12:36   ` [pve-devel] applied: " Thomas Lamprecht
2021-04-09  8:44 ` [pve-devel] [PATCH/RFC v2 container 7/7] restore: sanitize config: use new warn() function 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=20210409084436.2454-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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal