From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: yew-devel@lists.proxmox.com, Shannon Sterz <s.sterz@proxmox.com>
Subject: [yew-devel] applied: [PATCH yew-comp] user panel: don't submit raw "expire" field
Date: Tue, 16 Dec 2025 17:57:20 +0100 [thread overview]
Message-ID: <176590423481.492063.6561768026495160144.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251215133951.210548-1-s.sterz@proxmox.com>
On Mon, 15 Dec 2025 14:39:51 +0100, Shannon Sterz wrote:
> the api expects a unix timestamp here, but submitting the raw field
> will submit a rfc3999 timestamp. this happens when a user has expire
> set and is updated, but the expire field itself isn't changed. the ui
> would then submit the raw expire field. to fix this, don't submit the
> field by itself.
>
>
> [...]
Applied, thanks!
[1/1] user panel: don't submit raw "expire" field
commit: 808a5c0c6a8a4c7ec5a285c9d585425e98d84f6b
_______________________________________________
yew-devel mailing list
yew-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/yew-devel
prev parent reply other threads:[~2025-12-16 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 13:39 [yew-devel] " Shannon Sterz
2025-12-16 16:57 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=176590423481.492063.6561768026495160144.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=s.sterz@proxmox.com \
--cc=yew-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox