From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager] Jobs: don't schedule jobs with no computable next event
Date: Fri, 1 Apr 2022 16:48:07 +0200 [thread overview]
Message-ID: <aca8ba43-931b-7e8e-abba-2055dec500b3@proxmox.com> (raw)
In-Reply-To: <20220401112444.4166586-1-d.csapak@proxmox.com>
On 01.04.22 13:24, Dominik Csapak wrote:
> if we have a schedule that has no 'next event' we should skip the scheduling
> instead of schedule every round
>
> this can happen if someone sets an schedule that has no next match.
> some examples:
> * 2-31 00:00 (there is not February 31st)
> * mon 2022-04-02 (this would be a saturday, not monday)
> * 1970-1-1 (or every other exact date in the past)
>
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> PVE/Jobs.pm | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>
applied, thanks!
prev parent reply other threads:[~2022-04-01 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 11:24 [pve-devel] " Dominik Csapak
2022-04-01 14:48 ` 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=aca8ba43-931b-7e8e-abba-2055dec500b3@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pve-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.