I wasn't able to identify the license for parse-cron. :(

Could you let me know which license applies?

Hey, guys!

Is it possible to perform reversed lookup? Like, lets find nearest date in the past. Thx!

The following produces an incorrect last time:

cron_parser = CronParser.new('* * * * *')
p "Now: #{Time.now}"
p "Last: #{cron_parser.last}"
p "Next: #{cron_parser.next}"

The output is

"Now: 2014-05-12 13:15:42 -0600"
"Last: 2014-05-12 13:14:00 -0600"
"Next: 2014-05-12 13:16:00 -0600"

But would expect the output to be (notice 13:15:00 in the "Last:" line)

"Now: 2014-05-12 13:15:42 -0600"
"Last: 2014-05-12 13:15:00 -0600"
"Next: 2014-05-12 13:16:00 -0600"

I know the last commit is some time ago, but is there a chance this is still maintained?
There are some issues and I am wondering if I should report or fork and fix on my own.

Coud be fine to support "*/10 * * * *" means at every 10th minute: https://crontab.guru/#/10_*_

There is a bad calculation if I set more complex crontab. Here is an example.

2.2.4 :001 > require 'cron_parser'
=> true
2.2.4 :002 > require 'time'
=> true
2.2.4 :003 > cron_parser = CronParser.new('1 2 8-15 * 4')
=> #<CronParser:0x000000009644e8 @source="1 2 8-15 * 4", @time_source=Time>
2.2.4 :004 > cron_parser.next(Time.parse('2016-03-01 00:00'))
=> 2016-03-03 02:01:00 +0100

It should be '2016-03-10 02:01:00' I think.

Would you be able to push a version update so I can get the new changes with a gem update command?
Thanks!

I am packaging your gem for Fedora (being used in OpenNebula) and one minor issue is there is no License file in the gem.

Can you please include it this would be very appreciated.

Thanks,
Shawn

CronParser.new("1 1 1 1 1").next.strftime '%a' -> not a Monday
... CronParser.new("1 1 * 1 1").next.strftime '%a' works though

> CronParser.new("* * * * 100").next
=> 2021-11-01 00:00:00 +0100

Other fields seem to raise an exception if the field is out of bound

> CronParser.new("100 400 * * *").next
ArgumentError: argument out of range

from the tests it doesn't look like this syntax is supported

0 0 12 ? 1/1 MON#2 *

to mean midnight on the 2nd Monday of every month.

it was generated by http://www.cronmaker.com/

Hi,

CronParser#next is failing with some expressions. One example:

expression = "15-59/15 * * * *"
cron_parser = CronParser.new(expression)
next_execution_time = cron_parser.next(Time.now)

Trace:
ArgumentError: argument out of range
from /usr/lib/ruby/gems/1.9.1/gems/parse-cron-0.1.2/lib/cron_parser.rb:22:in local' from /usr/lib/ruby/gems/1.9.1/gems/parse-cron-0.1.2/lib/cron_parser.rb:22:into_time'
from /usr/lib/ruby/gems/1.9.1/gems/parse-cron-0.1.2/lib/cron_parser.rb:80:in next' from (irb):9 from /usr/lib/ruby/gems/1.9.1/gems/railties-3.0.5/lib/rails/commands/console.rb:44:instart'
from /usr/lib/ruby/gems/1.9.1/gems/railties-3.0.5/lib/rails/commands/console.rb:8:in start' from /usr/lib/ruby/gems/1.9.1/gems/railties-3.0.5/lib/rails/commands.rb:23:in<top (required)>'
from script/rails:6:in require' from script/rails:6:in

Thanks
Deepanshu Dialani

jruby-1.7.19 :001 > p = CronParser.new('0 5 * * 3-3',Time)
 => #<CronParser:0x52b28256 @source="0 5 * * 3-3", @time_source=Time> 
jruby-1.7.19 :002 > t=Time.utc(2016,"feb",21,0,0,0)
 => 2016-02-21 00:00:00 UTC 
jruby-1.7.19 :003 > t2 = p.next(t)
 => 2016-02-24 05:00:00 -0800 
jruby-1.7.19 :004 > p.next(t2)
 => 2016-02-25 05:00:00 -0800 

minor issue since whatever generates 3-3 is doing something weird to begin with but also kind of odd. most cron string parsers seem to collapse this into one entry.

I think following is a valid cron expression:
"50 21 ? * 3,6"

But cron-parser throws exception for it.

At the same time
50 21 * * 3,6

is invalid, but goes through without any exception.

need a require "set" somewhere

ruby 1.9.3p327 (2012-11-10 revision 37606) [x86_64-linux]
>> require 'cron_parser'
=> true
>> parser = CronParser.new('')
=> #<CronParser:0x000000021fc1e0 @source="">
>> e =  parser.parse_element('*', (Time.now..(Time.now + 60 * 60)))
NameError: uninitialized constant CronParser::Set
    from /home/jney/.gem/ruby/1.9.1/gems/parse-cron-0.1.1/lib/cron_parser.rb:124:in `parse_element'
    from (irb):4
    from /usr/bin/irb:12:in `<main>'

should submit a patch ?

The gem gives error when parsing 30 7 1-L/2 * *, in this case stands for last day of month.