Re: [PATCH datacenter-manager] ui: token_panel: show date and time correctly in token edit window

["Lukas Wagner" <l.wagner@proxmox.com>]

On Wed May 27, 2026 at 2:26 PM CEST, 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.
>
> Fix this by using our custom utility function from `proxmox_yew_comp`,
> which correctly formats the string as `YYYY-MM-DDTHH:mm` (without the
> timezone offset).
>
> Signed-off-by: Shan Shaji <s.shaji@proxmox.com>
> ---
>  ui/src/remotes/auto_installer/token_panel.rs | 14 +++++++++-----
>  1 file changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/ui/src/remotes/auto_installer/token_panel.rs b/ui/src/remotes/auto_installer/token_panel.rs
> index d213f39b..ebacc18c 100644
> --- a/ui/src/remotes/auto_installer/token_panel.rs
> +++ b/ui/src/remotes/auto_installer/token_panel.rs
> @@ -328,11 +328,15 @@ fn edit_input_panel(token: &AnswerToken) -> Html {
>              tr!("Expire"),
>              Field::new()
>                  .name("expire-at")
> -                .value(
> -                    token
> -                        .expire_at
> -                        .and_then(|exp| proxmox_time::epoch_to_rfc3339(exp).ok()),
> -                )
> +                .value(token.expire_at.and_then(|exp| {
> +                    let expiry_at = if exp == 0 {
> +                        String::new()
> +                    } else {
> +                        proxmox_yew_comp::utils::epoch_to_input_value(exp)
> +                    };
> +
> +                    Some(expiry_at)
> +                }))
>                  .placeholder(tr!("never"))
>                  .input_type(InputType::DatetimeLocal),
>          )

Was about to try to fix the same issue, but you were quicker :)

Can confirm that this fixes the issue:

Tested-by: Lukas Wagner <l.wagner@proxmox.com>