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 2A1721FF183 for ; Wed, 16 Jul 2025 00:18:32 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 45D5C104D2; Wed, 16 Jul 2025 00:19:30 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, pbs-devel@lists.proxmox.com, Christian Ebner Date: Wed, 16 Jul 2025 00:17:50 +0200 Message-ID: <175261786566.2452839.5494953215753705039.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.2 In-Reply-To: <20250623124543.590388-1-c.ebner@proxmox.com> References: <20250623124543.590388-1-c.ebner@proxmox.com> MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.033 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_MSPIKE_H2 0.001 Average reputation (+2) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pbs-devel] applied: [PATCH] docs: rephrase and extend rate limiting description for sync jobs 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-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pbs-devel-bounces@lists.proxmox.com Sender: "pbs-devel" On Mon, 23 Jun 2025 14:45:43 +0200, Christian Ebner wrote: > Since commit 37a85cf6 ("fix: ui: sync job: edit rate limit based on > sync direction") rate limits for sync jobs can be correctly applied > for both directions. State this in the documentation and explicitley > mention the directions to reduce confusion. > > Further, also mention the burst parameters, as they are not mentioned > at all. > > [...] Applied to master and stable-3, thanks! [1/1] docs: rephrase and extend rate limiting description for sync jobs commit: 4cba26673d72446bcc008e0aedc4eb7ca3fdac14 _______________________________________________ pbs-devel mailing list pbs-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel 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 78D051FF183 for ; Wed, 16 Jul 2025 00:18:34 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A7E5E104FB; Wed, 16 Jul 2025 00:19:30 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, pbs-devel@lists.proxmox.com, Christian Ebner Date: Wed, 16 Jul 2025 00:17:50 +0200 Message-ID: <175261786566.2452839.5494953215753705039.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.2 In-Reply-To: <20250623124543.590388-1-c.ebner@proxmox.com> References: <20250623124543.590388-1-c.ebner@proxmox.com> MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.033 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_MSPIKE_H2 0.001 Average reputation (+2) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] applied: [pbs-devel] [PATCH] docs: rephrase and extend rate limiting description for sync jobs X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" On Mon, 23 Jun 2025 14:45:43 +0200, Christian Ebner wrote: > Since commit 37a85cf6 ("fix: ui: sync job: edit rate limit based on > sync direction") rate limits for sync jobs can be correctly applied > for both directions. State this in the documentation and explicitley > mention the directions to reduce confusion. > > Further, also mention the burst parameters, as they are not mentioned > at all. > > [...] Applied to master and stable-3, thanks! [1/1] docs: rephrase and extend rate limiting description for sync jobs commit: 4cba26673d72446bcc008e0aedc4eb7ca3fdac14 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel