From: Fabian Ebner <f.ebner@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [pbs-devel] [PATCH-SERIES] improve warnings handling in UI and add to PVE
Date: Wed, 17 Mar 2021 09:33:09 +0100 [thread overview]
Message-ID: <51c3764f-a9cc-32cf-9f90-9f91624ddd85@proxmox.com> (raw)
In-Reply-To: <9c4faae1-e533-c992-43be-74d474c5c21d@proxmox.com>
Am 16.03.21 um 15:02 schrieb Dominik Csapak:
> series looks good to me, the only thing that might be not ideal
> is the value.replace('WARNINGS', '') call. it seems very brittle
> though in reality it will probably not be a problem
>
> Reviewed-By: Dominik Csapak <d.csapak@proxmox.com>
>
Thanks for the review. I'm also not 100% happy with the replace. I
didn't see a better alternative at the time, but maybe I do now:
We need to keep backwards compatibility for the existing callers of
parse_task_status(), so also returning the number of warnings there
doesn't seem to work. Instead, we could add a new
parse_task_status_full() that returns both the status *and* the text to
be displayed.
A better version of the replace would also be possible:
value.replace('WARNINGS', Proxmox.Utils.warningsText);
If one of those sounds sensible, I'll send a v2.
WARNING: multiple messages have this Message-ID
From: Fabian Ebner <f.ebner@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
pve-devel@lists.proxmox.com
Subject: Re: [pbs-devel] [PATCH-SERIES] improve warnings handling in UI and add to PVE
Date: Wed, 17 Mar 2021 09:33:09 +0100 [thread overview]
Message-ID: <51c3764f-a9cc-32cf-9f90-9f91624ddd85@proxmox.com> (raw)
In-Reply-To: <9c4faae1-e533-c992-43be-74d474c5c21d@proxmox.com>
Am 16.03.21 um 15:02 schrieb Dominik Csapak:
> series looks good to me, the only thing that might be not ideal
> is the value.replace('WARNINGS', '') call. it seems very brittle
> though in reality it will probably not be a problem
>
> Reviewed-By: Dominik Csapak <d.csapak@proxmox.com>
>
Thanks for the review. I'm also not 100% happy with the replace. I
didn't see a better alternative at the time, but maybe I do now:
We need to keep backwards compatibility for the existing callers of
parse_task_status(), so also returning the number of warnings there
doesn't seem to work. Instead, we could add a new
parse_task_status_full() that returns both the status *and* the text to
be displayed.
A better version of the replace would also be possible:
value.replace('WARNINGS', Proxmox.Utils.warningsText);
If one of those sounds sensible, I'll send a v2.
next prev parent reply other threads:[~2021-03-17 8:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 12:53 [pve-devel] " Fabian Ebner
2021-03-12 12:53 ` [pbs-devel] " Fabian Ebner
2021-03-12 12:53 ` [pve-devel] [PATCH widget-toolkit 1/6] tasks: add warningsText Fabian Ebner
2021-03-12 12:53 ` [pbs-devel] " Fabian Ebner
2021-03-12 12:53 ` [pve-devel] [PATCH proxmox-backup 2/6] ui: tasks: use warningsText Fabian Ebner
2021-03-12 12:53 ` [pbs-devel] " Fabian Ebner
2021-03-12 12:53 ` [pve-devel] [PATCH manager 3/6] ui: cluster task log: eslint fixes Fabian Ebner
2021-03-12 12:53 ` [pbs-devel] " Fabian Ebner
2021-03-16 13:53 ` [pve-devel] applied: " Dominik Csapak
2021-03-16 13:53 ` [pbs-devel] " Dominik Csapak
2021-03-12 12:53 ` [pve-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] " Fabian Ebner
2021-03-12 12:53 ` [pve-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] " Fabian Ebner
2021-03-12 12:53 ` [pve-devel] [PATCH/RFC container 6/6] restore: sanitize config: use new warn() function Fabian Ebner
2021-03-12 12:53 ` [pbs-devel] " Fabian Ebner
2021-03-16 14:02 ` [pve-devel] [pbs-devel] [PATCH-SERIES] improve warnings handling in UI and add to PVE Dominik Csapak
2021-03-16 14:02 ` Dominik Csapak
2021-03-17 8:33 ` Fabian Ebner [this message]
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=51c3764f-a9cc-32cf-9f90-9f91624ddd85@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=d.csapak@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 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.