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 53A591FF141 for ; Tue, 19 May 2026 21:34:38 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D110011913; Tue, 19 May 2026 21:34:28 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Gabriel Goller Subject: applied: [PATCH manager] sdn: fabrics: fix wireguard node "Allowed IPs" setValue Date: Tue, 19 May 2026 21:17:50 +0200 Message-ID: <177921827037.2471084.8338789122839388426.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260519154528.53144-1-g.goller@proxmox.com> References: <20260519154528.53144-1-g.goller@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1779219217558 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.004 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 SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: LL34MLX4HMFE3Z2L2B7E6C7QDWAFOXE3 X-Message-ID-Hash: LL34MLX4HMFE3Z2L2B7E6C7QDWAFOXE3 X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: David Riley X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Tue, 19 May 2026 17:44:32 +0200, Gabriel Goller wrote: > The setValue function on the "Allowed IPs" field on the wireguard fabric > node did not get removed correctly. When removing the content, we use > setRawValue, which only sets the displayed text and bypasses the form > change checks. Copied the fix from form/BandwidthSelector.js, looks a > bit ugly though because this is a named subclass, so callParent() > doesn't work. > > [...] Applied, thanks! [1/1] sdn: fabrics: fix wireguard node "Allowed IPs" setValue commit: 3288a07a4072c4c7379775c0fdf78252e3761f75