You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 11, 2019. It is now read-only.
most cron implementations authorize the use of leading zeros to improve readbility (and alignment).
When using a task in the form 01 * * * *, cronexpr complains about bad crontab line: 01 * * * *…
If I remove the leading zero, it works as expected.
Note : I'm using cronexpr through aptible/supercronic
i hope supercronic is not the culprit.
The text was updated successfully, but these errors were encountered:
I am having the same issue as well where it errors out when leading 0s is provided in the cron expression. It would be really nice to have the fix available to public.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
most cron implementations authorize the use of leading zeros to improve readbility (and alignment).
When using a task in the form
01 * * * *
, cronexpr complains aboutbad crontab line: 01 * * * *…
If I remove the leading zero, it works as expected.
Note : I'm using cronexpr through aptible/supercronic
i hope supercronic is not the culprit.
The text was updated successfully, but these errors were encountered: