GNU bug report logs - #75843
shepherd: cron-string->calendar-event does not accept "*/15 * * * *"

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Tomas Volf <~@wolfsden.cz>
Subject: bug#75843: closed (Re: bug#75843: shepherd: cron-string->calendar-event
 does not accept "*/15 * * * *")
Date: Wed, 05 Feb 2025 14:28:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#75843: shepherd: cron-string->calendar-event does not accept "*/15 * * * *"

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 75843 <at> debbugs.gnu.org.

-- 
75843: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=75843
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Ludovic Courtès <ludo <at> gnu.org>
To: Tomas Volf <~@wolfsden.cz>
Cc: 75843-done <at> debbugs.gnu.org
Subject: Re: bug#75843: shepherd: cron-string->calendar-event does not
 accept "*/15 * * * *"
Date: Wed, 05 Feb 2025 15:27:04 +0100

Hello,

Tomas Volf <~@wolfsden.cz> skribis:

> $ guix shell guile shepherd guile-fibers -- guile -c '(use-modules (shepherd service timer)) (cron-string->calendar-event "*/15 * * * *")'

[...]

>   1. &message: "\"*/15 * * * *\": invalid minutes cron field"

Fixed in 6f3860e492e078c5579e2117b04742252be81562.

> It seems to work with 0-59/15, so there possibly is some bug in handling
> the *.

Yup, that’s a good workaround until 1.0.2 is out (presumably in the
coming days).

Thanks,
Ludo’.

[Message part 3 (message/rfc822, inline)]

From: Tomas Volf <~@wolfsden.cz>
To: bug-guix <at> gnu.org
Subject: shepherd: cron-string->calendar-event does not accept "*/15 * * * *"
Date: Sat, 25 Jan 2025 23:09:00 +0100

[Message part 4 (text/plain, inline)]

Hello,

when I try to configure a timer based on my legacy crontab file, I get
the following error:

--8<---------------cut here---------------start------------->8---
$ guix shell guile shepherd guile-fibers -- guile -c '(use-modules (shepherd service timer)) (cron-string->calendar-event "*/15 * * * *")'
Backtrace:
In ice-9/boot-9.scm:
  1752:10  5 (with-exception-handler _ _ #:unwind? _ # _)
In unknown file:
           4 (apply-smob/0 #<thunk 7f5d9c401300>)
In ice-9/boot-9.scm:
    724:2  3 (call-with-prompt _ _ #<procedure default-prompt-handle…>)
In ice-9/eval.scm:
    619:8  2 (_ #(#(#<directory (guile-user) 7f5d9c404c80>)))
In ice-9/command-line.scm:
   185:19  1 (_ #<input: string 7f5d9c3fe850>)
In unknown file:
           0 (eval (cron-string->calendar-event "*/15 * * * *") #<di…>)

ERROR: In procedure eval:
ERROR:
  1. &message: "\"*/15 * * * *\": invalid minutes cron field"
--8<---------------cut here---------------end--------------->8---

It seems to work with 0-59/15, so there possibly is some bug in handling
the *.

Tomas

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.