public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>,
	Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup v2 5/6] ui: Dashboard/TaskSummary: add Verifies to the Summary
Date: Tue, 6 Oct 2020 13:25:12 +0200	[thread overview]
Message-ID: <a1482768-12e6-4768-6c51-e3990590f21a@proxmox.com> (raw)
In-Reply-To: <af43c0a6-2938-a697-ecdb-f62b915119b2@proxmox.com>

On 06.10.20 13:10, Thomas Lamprecht wrote:
> On 06.10.20 12:25, Dominik Csapak wrote:
>> and count every type that starts with 'verify' (e.g. verifyjob)
>>
>> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
>> ---
>>  www/Dashboard.js             | 6 ++++++
>>  www/dashboard/TaskSummary.js | 1 +
>>  2 files changed, 7 insertions(+)
>>
> 
> 
> I have some weird stuff going on here, namely, I get tasks with the same upid
> multiple times in the store??
> 
> This screws up the counts, e.g., verifies are counted all double,  gc are also
> more (but here not doubled!)
> 
> I.e., if I apply the below diff I get different numbers, now matching with the
> actual task list which opens when clicking on such a summary number..
> 
> diff --git a/www/Dashboard.js b/www/Dashboard.js
> index 1a68029f..0597194b 100644
> --- a/www/Dashboard.js
> +++ b/www/Dashboard.js
> @@ -150,7 +150,12 @@ Ext.define('PBS.Dashboard', {
>                 verify: { error: 0, warning: 0, ok: 0 },
>             };
> 
> +           let upid_seen = {};
>             records.forEach(record => {
> +               if (upid_seen[record.data.upid]) {
> +                   return;
> +               }
> +               upid_seen[record.data.upid] = 1;
>                 let type = record.data.worker_type;
>                 if (type === 'syncjob') {
>                     type = 'sync';
> 

ignore me, this is a side effect of left over from when I tried to reproduce some
task log active to index move behavior, I may have duplicated some tasks there by
accident.




  reply	other threads:[~2020-10-06 11:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-06 10:25 [pbs-devel] [PATCH proxmox-backup v2 1/6] api2/types: add TaskStateType struct Dominik Csapak
2020-10-06 10:25 ` [pbs-devel] [PATCH proxmox-backup v2 2/6] api2/status: add type- and statusfilter to tasks api call Dominik Csapak
2020-10-06 10:25 ` [pbs-devel] [PATCH proxmox-backup v2 3/6] ui: implment task history limit and make it configurable Dominik Csapak
2020-10-06 10:53   ` Thomas Lamprecht
2020-10-06 11:25     ` Dominik Csapak
2020-10-06 10:25 ` [pbs-devel] [PATCH proxmox-backup v2 4/6] ui: Dashboard/TaskSummary: refactor types and title Dominik Csapak
2020-10-06 10:25 ` [pbs-devel] [PATCH proxmox-backup v2 5/6] ui: Dashboard/TaskSummary: add Verifies to the Summary Dominik Csapak
2020-10-06 11:10   ` Thomas Lamprecht
2020-10-06 11:25     ` Thomas Lamprecht [this message]
2020-10-06 10:25 ` [pbs-devel] [PATCH proxmox-backup v2 6/6] ui: Dashboard/TaskSummary: show task overlay when clicking on a count Dominik Csapak
2020-10-06 14:07 ` [pbs-devel] applied-series: [PATCH proxmox-backup v2 1/6] api2/types: add TaskStateType struct Thomas Lamprecht

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=a1482768-12e6-4768-6c51-e3990590f21a@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=d.csapak@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal