From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 8E9B71FF165 for ; Thu, 6 Nov 2025 10:13:21 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BF9A310F8B; Thu, 6 Nov 2025 10:14:02 +0100 (CET) Message-ID: <410d0f1d-1e35-4828-8e9a-8cd722f3cb0e@proxmox.com> Date: Thu, 6 Nov 2025 10:13:28 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: pbs-devel@lists.proxmox.com References: <20251105155129.517430-1-n.frey@proxmox.com> <20251105155129.517430-5-n.frey@proxmox.com> Content-Language: en-US, de-DE From: Christian Ebner In-Reply-To: <20251105155129.517430-5-n.frey@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1762420390124 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.047 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pbs-devel] [PATCH proxmox-backup 3/4] api: verify: add worker-threads to update endpoint X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox Backup Server development discussion Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: pbs-devel-bounces@lists.proxmox.com Sender: "pbs-devel" Again a short commit message would be nice, e.g. Allows to add, update or delete the worker-thread property in the verify job config via the API. This will control the number of workers to read (and verify?) chunks in the verification job. On 11/5/25 4:51 PM, Nicolas Frey wrote: > Signed-off-by: Nicolas Frey > --- > src/api2/config/verify.rs | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --git a/src/api2/config/verify.rs b/src/api2/config/verify.rs > index e71e0c2e..2847c984 100644 > --- a/src/api2/config/verify.rs > +++ b/src/api2/config/verify.rs > @@ -149,6 +149,8 @@ pub enum DeletableProperty { > Ns, > /// Delete max-depth property, defaulting to full recursion again > MaxDepth, > + /// Delete worker-threads property > + WorkerThreads, > } > > #[api( > @@ -229,6 +231,9 @@ pub fn update_verification_job( > DeletableProperty::MaxDepth => { > data.max_depth = None; > } > + DeletableProperty::WorkerThreads => { > + data.worker_threads = None; > + } > } > } > } > @@ -266,6 +271,9 @@ pub fn update_verification_job( > data.max_depth = Some(max_depth); > } > } > + if update.worker_threads.is_some() { > + data.worker_threads = update.worker_threads; > + } > > // check new store and NS > user_info.check_privs(&auth_id, &data.acl_path(), PRIV_DATASTORE_VERIFY, true)?; _______________________________________________ pbs-devel mailing list pbs-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel