Closed popmonkey closed 8 years ago
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.
3-3
looks like this was fixed along the way - 0.1.4 works fine
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.