-
Notifications
You must be signed in to change notification settings - Fork 482
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
resque-scheduler (4.3.1) bug with rufus-scheduler (3.5.0) #649
Comments
Same for us, |
Related has anyone confirmed if |
Has anyone figured this out? |
still seems to be an issue, I've just bumped into this with rufus-scheduler 3.5.2 |
Sounds like that should've been a rufus-scheduler 4.0.0 release. As a workaround, resque-scheduler 4.4.1 could require rufus-scheduler ~> 3.2, < 3.5 and resque-scheduler 5.0.0 would use rufus-scheduler ~> 3.5. But that may break those who've already upgraded to rufus-scheduler 3.5+ and changed their cron lines… |
Regarding the specific cases above, it appears the parser just got stricter. But the exception is misleading.
Nonstandard syntax. Should be
That doesn't work. It means run every minute Think you'll need to omit the schedule rather than using cron syntax to not run it. |
Released fugit 1.2.0. It accepts the non-standard "/15 * * * *". Released rufus-scheduler 3.6.0 which fails on invalid cron strings, with a better error message. Fugit is the parsing library used by rufus-scheduler. |
Hi,
This happens when it tries to start schedule from scheduler file,
cron type:
when I locked
rufus-scheduler '~> 3.4.2'
in gemfile, it was solvedThanks,
Niko
The text was updated successfully, but these errors were encountered: