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 E326E1FF137 for ; Sat, 16 May 2026 20:59:52 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 149D632A14; Sat, 16 May 2026 20:59:44 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Stefan Hanreich Subject: applied: [PATCH pve-manager 1/1] sdn: wg interface panel: fix rendering peer list in chrome Date: Sat, 16 May 2026 20:59:19 +0200 Message-ID: <177895794538.244346.17427322023431878563.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260515152940.449246-1-s.hanreich@proxmox.com> References: <20260515152940.449246-1-s.hanreich@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: 1778957966251 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: TVGGGZR4SQ2DIMWEPOR3W74Q6YNNEA7S X-Message-ID-Hash: TVGGGZR4SQ2DIMWEPOR3W74Q6YNNEA7S 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 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 Fri, 15 May 2026 17:29:39 +0200, Stefan Hanreich wrote: > Rendering the peer list only worked in Firefox, but not chrome-based > browsers. This was caused by a race condition when setting the > availablePeers and selectedPeers property of the WireGuard > PeerSelectionPanel. Rendering the list only worked when the > availablePeers were set before the selectedPeers, because the peer > list was generated in the setSelectedPeers method, which gets invoked > when the selectedPeers config property gets set. If the availablePeers > property gets set afterwards, then the selectedPeers method does not > generate any entry because availablePeers is empty and the for loop in > setSelectedPeers is a no-op. > > [...] Applied, thanks! [1/1] sdn: wg interface panel: fix rendering peer list in chrome commit: 5cc53243bb5b4c17b1a17e62a60217a75521e142