-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please update cron-utils dependency #4
Comments
That sounds reasonable. Would you mind testing a current snapshot build in your application? I've just deployed the latest build with upgraded cron-utils dependency as |
Sure! Will let you know the results. Thank you!
// Bas
Verstuurd vanaf mijn iPhone
Op 19 dec. 2018 om 07:45 heeft Simon Taddiken <[email protected]>
het volgende geschreven:
That sounds reasonable. Would you mind testing a current snapshot build in
your application? I've just deployed the latest build with upgraded
cron-utils dependency as 1.2.1-SNAPSHOT
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAFYqaHiWDxoHeKYsUt2vjUki0Yf66Qdks5u6eBwgaJpZM4ZZCfz>
.
|
Please note it fixes another bug we encountered: cron-utils 5.0.0 contains a bug where executions on the last day of the month are skipped: When do you expect to make a new release? Ideally we have one before the end of the month so we don't run into the cron-utils issue mentioned above. Thanks! |
You can expect the release either wthin the next few hours or at least
within the next days.
Sebastian Gooren <[email protected]> schrieb am Do., 20. Dez. 2018,
16:32:
… 1.2.1-SNAPSHOT works fine for me 👍
Please note it fixes another bug we encountered: cron-utils 5.0.0 contains
a bug where executions on the last day of the month are skipped:
jmrozanec/cron-utils#117
<jmrozanec/cron-utils#117>
When do you expect to make a new release? Ideally we have one before the
end of the month so we don't run into the cron-utils issue mentioned above.
Thanks!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AATW-y3UKuKRXs7S4gIOk7ADcQbrBsEeks5u662LgaJpZM4ZZCfz>
.
|
Much appreciated 👍 |
Released as |
Hi!
We're getting a stack trace logged when we add scheduled methods which have comma-separated fields (e.g. "0 0,30 * ? * *").
This was fixed in cron-utils 5.0.5 (see jmrozanec/cron-utils#125).
Can you please update the cron-utils dependency? The 5.0.0 dependency is from august 2016 in any case, which is quite old. They are at version 8.0.0 already.
The text was updated successfully, but these errors were encountered: