1.month schedule with a typo in at: silently succeeds with wrong date

[ctrlrsf]

A typo such as 'Aug 31sh 11:00pm' in the at: parameter for a 1.month crontab creates a wrong crontab entry.

Generated crontab has 1 in the day of month field:

0 23 1 * * /bin/bash -l -c 'echo test'

Would be nice if whenever existed with non-zero for typos like this. Willing to work on fix for this if I could get some guidance.

[benlangfeld]

➭ be irb
>> require 'chronic'
=> true
>> Chronic.parse 'Aug 31sh 11:00pm'
=> 2016-08-01 23:00:00 -0400

It looks like this is actually an issue with Chronic (which we use here). It looks like they don't support such a thing. Could you file an issue over there referencing this one?

[ctrlrsf]

Thanks for the pointer. Will do!