Commands being incorrectly parsed
MutantOctopus opened this issue · 4 comments
Hi. I fairly like this bot, but I've found a bit of trouble in using it. Oftentimes it fails to correctly process commands, setting them a day and an hour ahead of schedule. It works fine if you specify "in five minutes", but it fails when presented a "today at 11:00PM" command, which, when today is 3/12/16, will record an event for "14.03.2016 at 00:00:00". Similarly, "today at 7:30" returned "13.03.2016 at 20:30:00". However, "tomorrow at 12:00" will return the correct date, 13.03.2016, but not the correct time, which is still "13:00:00". This bot has a lot of potential, but needs this to be fixed before I can give it the recognition it deserves.
Hello, maybe it deals with timezones. What is your current timezone on device/bot?
US/New York, but I tested it out and waited for an alarm to go off, and it went off at exactly the time it had specified, which was indeed a day and an hour past what I wanted
I researched that you had timechanges 13.03.2016 in NewYork http://www.timeanddate.com/time/change/usa/new-york
So please past here screenshots with bot dialog. Therefore I can inspect in which time moment you set notifications.
I lost the old records but when I test it now it seems like it's working... Maybe it was just because of the upcoming Daylight Savings Time. If another issue comes up I'll bring it to your attention. Although -
I was a bit surprised that this set the alert for tomorrow at 5AM instead of today at 5PM. It's not so much a "functionality failure", but it would be useful for English-speaking users if the "Today/tonight at 5" command would parse it as 5PM.
Thanks