From: Stefan Lendl <s.lendl@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: Re: [pbs-devel] [PATCH proxmox-backup v3] api: make prune-group a real workertask
Date: Tue, 12 Mar 2024 11:30:52 +0100 [thread overview]
Message-ID: <87a5n32143.fsf@gmail.com> (raw)
In-Reply-To: <20240308133625.32282-1-g.goller@proxmox.com>
LGTM with a slight note below for a style preference.
> + let prune_group = move |worker: Arc<WorkerTask>| {
> + if keep_all {
> + task_log!(worker, "No prune selection - keeping all files.");
> + } else {
You don't actually need to spawn a task if you're not doing any work.
On the other hand it makes the code slightly simpler and you need the
worker, right?
> + let mut opts = Vec::new();
> + if !ns.is_root() {
> + opts.push(format!("--ns {ns}"));
> + }
> + crate::server::cli_keep_options(&mut opts, &keep_options);
> +
> + task_log!(worker, "retention options: {}", opts.join(" "));
> + task_log!(
> + worker,
> + "Starting prune on {} group \"{}\"",
> + print_store_and_ns(&store, &ns),
> + group.group(),
> + );
> }
> - crate::server::cli_keep_options(&mut opts, &keep_options);
> -
> - task_log!(worker, "retention options: {}", opts.join(" "));
> - task_log!(
> - worker,
> - "Starting prune on {} group \"{}\"",
> - print_store_and_ns(&store, &ns),
> - group.group(),
> - );
> - }
>
> - for (info, mark) in prune_info {
> - let keep = keep_all || mark.keep();
> + for (info, mark) in prune_info {
> + let keep = keep_all || mark.keep();
> + let backup_dir = &info.backup_dir;
You wouldn't have to handle keep_all here.
You're handling dry_run separatly already as well.
next prev parent reply other threads:[~2024-03-12 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 13:36 Gabriel Goller
2024-03-12 10:30 ` Stefan Lendl [this message]
2024-03-12 13:07 ` Gabriel Goller
2024-04-02 11:14 ` Stefan Lendl
2024-04-09 9:04 ` Gabriel Goller
2024-04-09 10:44 ` [pbs-devel] applied: " 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=87a5n32143.fsf@gmail.com \
--to=s.lendl@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