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 5A9ED1FF136 for ; Mon, 09 Mar 2026 21:09:17 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 10B6B9B60; Mon, 9 Mar 2026 21:09:10 +0100 (CET) From: Thomas Lamprecht To: pdm-devel@lists.proxmox.com, Lukas Wagner Subject: applied: [PATCH proxmox-yew-comp v6 2/2] loadable component: don't trigger reload when starting a task Date: Mon, 9 Mar 2026 21:08:56 +0100 Message-ID: <177308688529.191170.17924934496322969088.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260309083640.49044-3-l.wagner@proxmox.com> References: <20260309083640.49044-1-l.wagner@proxmox.com> <20260309083640.49044-3-l.wagner@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: 1773086914985 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.017 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: ZGXYPHVH63N2I33Z63AK5O7BUCHAX2EV X-Message-ID-Hash: ZGXYPHVH63N2I33Z63AK5O7BUCHAX2EV 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 Datacenter Manager development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Mon, 09 Mar 2026 09:36:35 +0100, Lukas Wagner wrote: > The view will be reloaded anyways when the task viewer closes. > > Usually, one wants to start a new task to produce/refresh some data > which should later be displayed in the component, so it makes little > sense to reload before the task actually finishes. > > This avoids an issue with the previous commit. The double-load would > reset 'fresh_load' after the first load, leading to the new data not > being correctly displayed after the second load. > > [...] Applied, thanks! [2/2] loadable component: don't trigger reload when starting a task commit: ad1d0361f3e5c1c17fb4b54baa3555f99afd9414