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 EBF5D1FF140 for ; Fri, 27 Mar 2026 00:24:59 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BDFD91EA20; Fri, 27 Mar 2026 00:25:22 +0100 (CET) From: Thomas Lamprecht To: yew-devel@lists.proxmox.com, Shannon Sterz Subject: applied: [PATCH yew-comp] user panel: handle expire property on edit properly Date: Fri, 27 Mar 2026 00:24:42 +0100 Message-ID: <177456748010.2605442.11705893059598670797.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260325121516.164312-1-s.sterz@proxmox.com> References: <20260325121516.164312-1-s.sterz@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: 1774567439945 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.011 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 Message-ID-Hash: ZZCSG3WS6EFQKDKU45L4RYX4W6HXLT5B X-Message-ID-Hash: ZZCSG3WS6EFQKDKU45L4RYX4W6HXLT5B 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: Yew framework devel list at Proxmox List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Wed, 25 Mar 2026 13:15:16 +0100, Shannon Sterz wrote: > setting expire to "0" is a special case meaning "never expires". while > this was honored in the user management overview, the edit panel > rendered this as 01.01.1970 00:00:00 UTC, or the Unix epoch. this had > minimal functional impact, but it may be confusing to users. set > expire to `Value::Null` in this special case, rendering a cleared date > picker. > > [...] Applied, thanks! [1/1] user panel: handle expire property on edit properly commit: fc2c392666fa56f005dbd3cbf4af100dc6344be9