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 178BF1FF13A for ; Wed, 27 May 2026 16:02:18 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 234A11E982; Wed, 27 May 2026 16:02:15 +0200 (CEST) From: Thomas Lamprecht To: pdm-devel@lists.proxmox.com, Shan Shaji Subject: applied: [PATCH datacenter-manager] ui: token_panel: show date and time correctly in token edit window Date: Wed, 27 May 2026 16:02:03 +0200 Message-ID: <177989052269.302828.9190112230461206331.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260527122639.319204-1-s.shaji@proxmox.com> References: <20260527122639.319204-1-s.shaji@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: 1779890504055 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.005 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: RZRZZ5NFD22BVV23ZESOWKR62CKRG4AX X-Message-ID-Hash: RZRZZ5NFD22BVV23ZESOWKR62CKRG4AX 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 Wed, 27 May 2026 14:26:39 +0200, Shan Shaji wrote: > Fix an issue where the currently selected token expiry date was not > displayed in the token edit window. > > This occurred because `epoch_to_rfc3339` returns a string containing > timezone information, which is unsupported by the HTML `datetime-local` > input element. As a result, the element failed to parse and show the > current value. > > [...] Applied, thanks! [1/1] ui: token_panel: show date and time correctly in token edit window commit: 2b9297be161df9f0b3f6a1d42de86ff393736abd