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 ACC461FF185 for ; Mon, 17 Nov 2025 18:08:42 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id C6480495; Mon, 17 Nov 2025 18:08:45 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Dominik Csapak Date: Mon, 17 Nov 2025 18:04:52 +0100 Message-ID: <176339909014.3857420.3869143605583980826.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20251117153721.3161092-1-d.csapak@proxmox.com> References: <20251117153721.3161092-1-d.csapak@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1763399263862 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.023 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] ui: resource tree: render clustername consistently 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, 17 Nov 2025 16:37:14 +0100, Dominik Csapak wrote: > since we changed the tree to create the store outside the component on > first load, setting the clustername on the root element of the tree > could be race against the recreation of that node on the first load. > > This made the display of the cluster name inconsistent, iow. sometimes > the clustername vanished after the first load. > > [...] Applied, thanks! I wasn't sure if I had the separate function back when I added this to also cope with a new cluster create showing up faster (on next login), but tbh., not sure at all (about that having worked nor that being really a goal), just wanted to put it out the in case I remember more of it (or in the unlikely case that we get some report about this). [1/1] ui: resource tree: render clustername consistently commit: 5d345fab0b48d9e9da820cb45c98bf8a3dc71b68 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel