From: Dominik Csapak <d.csapak@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup 2/3] ui: datastore/Content: improve verification actions
Date: Thu, 27 Jan 2022 15:13:20 +0100 [thread overview]
Message-ID: <20220127141321.1072674-2-d.csapak@proxmox.com> (raw)
In-Reply-To: <20220127141321.1072674-1-d.csapak@proxmox.com>
verifying a single snapshot is now never skipped because of recent verify
verifying a group will now reverify after 29 days to be consistent
with the 'All OK (old)' display
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
www/datastore/Content.js | 2 ++
1 file changed, 2 insertions(+)
diff --git a/www/datastore/Content.js b/www/datastore/Content.js
index 5aaec85c..d0498bc7 100644
--- a/www/datastore/Content.js
+++ b/www/datastore/Content.js
@@ -388,11 +388,13 @@ Ext.define('PBS.DataStoreContent', {
"backup-type": data["backup-type"],
"backup-id": data["backup-id"],
"backup-time": (data['backup-time'].getTime()/1000).toFixed(0),
+ "outdated-after": 0, // always reverify single snapshots
};
} else {
params = {
"backup-type": data.backup_type,
"backup-id": data.backup_id,
+ "outdated-after": 29, // reverify after 29 days so match with the "old" display
};
}
--
2.30.2
next prev parent reply other threads:[~2022-01-27 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 14:13 [pbs-devel] [PATCH proxmox-backup 1/3] verify: allow '0' days for reverification Dominik Csapak
2022-01-27 14:13 ` Dominik Csapak [this message]
2022-01-27 14:33 ` [pbs-devel] applied: [PATCH proxmox-backup 2/3] ui: datastore/Content: improve verification actions Thomas Lamprecht
2022-01-27 14:13 ` [pbs-devel] [PATCH proxmox-backup 3/3] ui: datastore/Content: add 'Re-Verify after (days)' input to 'Verify All' Dominik Csapak
2022-01-27 14:32 ` [pbs-devel] applied: [PATCH proxmox-backup 1/3] verify: allow '0' days for reverification 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=20220127141321.1072674-2-d.csapak@proxmox.com \
--to=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