From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 2A2C81FF17E for ; Thu, 11 Dec 2025 14:11:39 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id F369015C53; Thu, 11 Dec 2025 14:12:18 +0100 (CET) From: Fiona Ebner To: pve-devel@lists.proxmox.com, Dominik Csapak Date: Thu, 11 Dec 2025 14:11:58 +0100 Message-ID: <176545871245.157948.11489765545313959210.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20251205100317.1101549-1-d.csapak@proxmox.com> References: <20251205100317.1101549-1-d.csapak@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1765458733922 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.016 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: [pve-devel] applied: [PATCH manager v2] api: workaround broken 'maxworkers' alias in bulk actions api calls 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 Fri, 05 Dec 2025 11:02:39 +0100, Dominik Csapak wrote: > It seems, that 'alias' schema does not properly work currently for > normal schema definitions (only for property-string), since it does not > verification of the actual schema (checked by calling the api with > maxworkers=1000, which throws no errors). Luckily, this is the only use > of alias for api parameters that I could find. For the new cluster wide > api calls it did not do anything, since we did not actually use > `$param->{maxworkers}`, but for the node specific one broke the UI, > since there we still send 'maxworkers', but the backend did not use that > anymore. > > [...] Applied, thanks! [1/1] api: workaround broken 'maxworkers' alias in bulk actions api calls commit: 60a0f0f0e81176c763f60c17c301791efda347d7 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel