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 EC5AE1FF13C for ; Thu, 02 Apr 2026 13:37:52 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 71FE214BDC; Thu, 2 Apr 2026 13:38:22 +0200 (CEST) From: Dominik Csapak To: pve-devel@lists.proxmox.com, Shan Shaji Subject: applied: [pve-devel] [PATCH pve_flutter_frontend] fix: ui: token expiry showing unix epoch time Date: Thu, 2 Apr 2026 13:37:41 +0200 Message-ID: <177512982846.2433801.6873476906649804207.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20251230154819.264985-1-s.shaji@proxmox.com> References: <20251230154819.264985-1-s.shaji@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -1.454 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 1 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 1 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 1 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 Message-ID-Hash: FDSARFFV2GLCVGSYJJS2WTLJANKFCQMU X-Message-ID-Hash: FDSARFFV2GLCVGSYJJS2WTLJANKFCQMU X-MailFrom: d.csapak@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 Tue, 30 Dec 2025 16:48:19 +0100, Shan Shaji wrote: > When the token expiry is set to 'never', the API returns 0 for the > expire property. After deserialization, this property was being > populated with the Unix epoch time. To fix this, added an additional > check and updated the label to align with our web UI. > > Applied, thanks! [1/1] fix: ui: token expiry showing unix epoch time commit: ad3a819c68ff15a442772e9e13e0ebe3dbb380ce