From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>
Cc: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox 1/3] time: Add traits to DateTimeValue and TimeSpec
Date: Wed, 13 Aug 2025 14:38:23 +0200 [thread overview]
Message-ID: <s8oh5ybz9a8.fsf@proxmox.com> (raw)
In-Reply-To: <2dd6c172-d3d4-4770-8b8e-0431d3209db6@proxmox.com> (Fiona Ebner's message of "Wed, 13 Aug 2025 14:31:25 +0200")
Fiona Ebner <f.ebner@proxmox.com> writes:
> Am 13.08.25 um 1:26 PM schrieb Maximiliano Sandoval:
>>
>> Maximiliano Sandoval <m.sandoval@proxmox.com> writes:
>>
>>> which are useful for tests.
>>>
>>> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
>>> ---
>>> proxmox-time/src/calendar_event.rs | 1 +
>>> proxmox-time/src/date_time_value.rs | 2 +-
>>> 2 files changed, 2 insertions(+), 1 deletion(-)
>>
>> In a support case we found a system with 40:00 as a schedule in a backup
>> job. It is possible to entire this calendar event on the web UI.
>>
>> After this series the web UI won't allow it anymore with an error:
>>
>> ```
>> Parameter verification failed. (400)
>>
>> schedule: invalid format - invalid calendar event '40:00' - unable to parse calendar event at ':00' - Nom(Eof)
>> ```
>>
>
> Note that we have the same behavior in Proxmox VE:
> https://bugzilla.proxmox.com/show_bug.cgi?id=6161
>
> If it is changed, it should be made consistent between products.
> Unfortunately, this one got missed before the major releases, as one
> could consider this a breaking change.
The Proxmox VE web UI uses this crate so it would be consistent, I
tested the change against it.
I can do a v2 referencing the bugzilla entry, and add a test for "24:00"
which returns an error with this patch (as it should).
--
Maximiliano
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-08-13 12:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 11:03 Maximiliano Sandoval
2025-08-13 11:03 ` [pbs-devel] [PATCH proxmox 2/3] time: Split parse_time_spec parser into two Maximiliano Sandoval
2025-08-13 11:03 ` [pbs-devel] [PATCH proxmox 3/3] time: Add more calendat event tests Maximiliano Sandoval
2025-08-13 11:22 ` [pbs-devel] [PATCH proxmox 1/3] time: Add traits to DateTimeValue and TimeSpec Maximiliano Sandoval
2025-08-13 11:26 ` Maximiliano Sandoval
2025-08-13 11:27 ` Dominik Csapak
2025-08-13 11:30 ` Maximiliano Sandoval
2025-08-13 11:32 ` Dominik Csapak
2025-08-13 12:31 ` Fiona Ebner
2025-08-13 12:38 ` Maximiliano Sandoval [this message]
2025-08-13 12:41 ` Fiona Ebner
2025-08-13 13:07 ` [pbs-devel] superseded: " Maximiliano Sandoval
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=s8oh5ybz9a8.fsf@proxmox.com \
--to=m.sandoval@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pbs-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