Shepherd calendar event bug

[Ludovic Courtès]

Felix Lechner <felix.lechner@lease-up.com> skribis:

> Okay, then there is still another problem.  I am unable to reconfigure
> my systems via 'guix deploy' when a timer is enabled already.  I am
> trying to add a second timer.

[...]

>    (start #~(make-timer-constructor
>              ;; Every first Sunday of the month at 1 AM.
>              (calendar-event #:days-of-month '(1 2 3 4 5 6 7)
>                              #:days-of-week '(sunday)
>                              #:hours '(1))

I was able to reproduce the issue with current ‘devel’:

--8<---------------cut here---------------start------------->8---
scheme@(shepherd service timer)> (next-calendar-event (calendar-event 
#:days-of-month '(1 2 3 4 5 6 7)
                             #:days-of-week '(sunday)
                             #:hours '(1))
                                                      (time-utc->date 
(current-time time-utc)))
ice-9/boot-9.scm:1676:22: In procedure raise-exception:
Throw to key `match-error' with args `("match" "no matching pattern" ())'.

Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.
scheme@(shepherd service timer) [1]> ,bt
In shepherd/service/timer.scm:
    327:8  2 (next-calendar-event #<<calendar-event> seconds: (0) minutes: (0 1 
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 
31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 
57 58 59) hours: (1) days-of-month: (1 2 3 4 5 6 7) months: (1 2 3 4 5 6 7 8 9 
10 11 12) days-of-week: (0)> _)
    252:4  1 (fit-day _ _ _)
In ice-9/boot-9.scm:
  1676:22  0 (raise-exception _ #:continuable? _)
--8<---------------cut here---------------end--------------->8---

Note that this is asking for a Sunday 1st, or 2nd, etc. until 7th,
contrary to what the comment says.

It should be able to find Sunday, Sept. 1st at least.

I’ll investigate but in the meantime maybe what you want is to remove
#:days-of-month?

Ludo’.