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
Current date is Sat Aug 18 21:05:30 EDT 2018
Last commit is Sat Aug 18 20:50:32 2018 -0400
Expected: Last commit: 15 minutes ago
Observed: Last commit: -1 months ago
any_good paper_trail
# ...
Last commit: -1 months ago
...last closed: -1 months ago
# ...
date
Sat Aug 18 21:05:30 EDT 2018
git show
commit b0e4477864096832b57c1ef9edc0543f286fdaeb (HEAD -> master, origin/master, origin/HEAD)
Date: Sat Aug 18 20:50:32 2018 -0400
The text was updated successfully, but these errors were encountered:
That's funny :( Playing with dates and times and can't guess how this bug could emerge.
Please tell me if you'll see the same thing again (and if it is not too much to ask, can you show what exactly Time.now will show in irb at this time).
I expect this can only be reproduced within a certain time window after a gem is released, so I'll try to remember to test again the next time I release something.
Thanks! The bug looks definitely like related to timezones, but I played with different gems and dates, and everything seems to work well, some weird edge case I can't guess.
Current date is Sat Aug 18 21:05:30 EDT 2018
Last commit is Sat Aug 18 20:50:32 2018 -0400
Expected: Last commit: 15 minutes ago
Observed: Last commit: -1 months ago
The text was updated successfully, but these errors were encountered: