You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Bug #1730: Commit timestamps (eg. in repo#show) seem to be off by about 6 hours

Kind bug
Product wincent.dev
When Created , updated
Status closed
Reporter Greg Hurrell
Tags no tags

Description

Just noticed this: commits made here less than an hour ago, and with the correct timestamp information locally when viewed using git log, show up in the repo browser as being about 6 hours ago.

Just to be sure I'm not going mad, checked the remote server that I'm pushing into, and the timestamps are (of course) still correct there.

Probably something to do with the machine being in a different timezone (by about 6 hours...)

Comments

  1. Greg Hurrell

    Yep, still happening.

    Stuff which I committed at 21:30 in my local timezone is showing up as 3 hours in the future in the repo browser (ie. 12:30 AM). That would be right if I were making the commits in New York, but I'm not.

    How I see the commit in git log in San Francisco: 

    Date:   Sat Mar 26 21:31:36 2011 -0700

    That's correct (and we're 7 hours behind GMT).

    How I see the commit in the browser (with JavaScript turned on): 

    March 27, 2011 12:31:36 AM PDT

    So it's reporting Pacific Daylight Time there.

    How I see it with JavaScript turned off:

    2011-03-27 07:31:36 UTC
  2. Greg Hurrell

    And just for reference, how I git log looks on the server: 

    Date:   Sat Mar 26 21:31:36 2011 -0700

    Where the time as reported by date is currently: 

    Sun Mar 27 01:39:41 EDT 2011

    Compared to date on my local machine:

    Sat Mar 26 22:40:01 PDT 2011
  3. Greg Hurrell

    Fixed. Will go out with next deploy, most likely. (Not 100% sure, as I currently have two branches ready to go, one for Rails 3.0.8.rc2 and the other for 3.1.0.rc1; not sure which one will be go out first, and I've only made the fix on the Rails 3.1.0.rc1 branch so far.)

  4. Greg Hurrell

    Status changed:

    • From: new
    • To: closed
Add a comment

Comments are now closed for this issue.

Menu