You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#1002 promised to fix #403 and has been merged to master. As I discovered now it is only a partial fix.
Recall the issue was the dateparser would skip ahead a day if the time had already passed in UTC when preferring dates from the future. For example parsing 6pm EST (11pm UTC) at 10pm UTC would return tomorrow 11pm, instead of today 11pm UTC.
#1002 addresses this by passing the time zone so the correct relative base can be computed. What I didn't realize at the time is that ptz is only the time zone popped off the string. So, if the timezone is supplied via settings instead, nothing is passed along and the old bug from #403 reappears.
I might submit a pull request in the future but I wanted to report it already.
#1002 promised to fix #403 and has been merged to master. As I discovered now it is only a partial fix.
Recall the issue was the dateparser would skip ahead a day if the time had already passed in UTC when preferring dates from the future. For example parsing 6pm EST (11pm UTC) at 10pm UTC would return tomorrow 11pm, instead of today 11pm UTC.
#1002 addresses this by passing the time zone so the correct relative base can be computed. What I didn't realize at the time is that ptz is only the time zone popped off the string. So, if the timezone is supplied via settings instead, nothing is passed along and the old bug from #403 reappears.
I might submit a pull request in the future but I wanted to report it already.
Versions:
Minimum working example:
The text was updated successfully, but these errors were encountered: