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 5BBC11FF136 for ; Mon, 04 May 2026 20:04:14 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 78EA2EFCA; Mon, 4 May 2026 20:04:11 +0200 (CEST) From: Thomas Lamprecht To: pbs-devel@lists.proxmox.com, Christian Ebner Subject: applied: [PATCH proxmox-backup v2] api: node: fix task view by returning optional endtime in tasks status Date: Mon, 4 May 2026 20:03:58 +0200 Message-ID: <177791783512.3062238.1873551566104642626.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260504154346.901478-1-c.ebner@proxmox.com> References: <20260504154346.901478-1-c.ebner@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: 1777917741348 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.003 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: HZNO4MNAEF7YQOMWSZFEFWPU43OX7FCI X-Message-ID-Hash: HZNO4MNAEF7YQOMWSZFEFWPU43OX7FCI 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 Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Mon, 04 May 2026 17:43:46 +0200, Christian Ebner wrote: > With the intention to correctly show the task end time without > relying on further API calls or workarounds to gather it. > > Whenever the task is considered finished, return the endtime > according to the parsed TaskState. > > Same issue as tackled by commit e8552dae3 ("ui: sync/verify view: > show correct duration in task log window"), but since commit > 7431c0766 ("window: TaskViewer: derive endtime from polled status > when not provided") in proxmox-widget-toolkit we can rely on the > task viewer to get the endtime by itself > > [...] Applied, thanks! [1/1] api: node: fix task view by returning optional endtime in tasks status commit: 2683bca432f934d032aa709ed9c690302ab564d5