Why does Fisheye show my last commit date as '31 Dec 69'

[Dave]

We are using subversion as our repository, and have indexed starting from about 18 months ago.  I was 3 years old in 1969, so I am sure I did not make a commit at that time.  What gives?

fisheye svn commits.PNG

Update:

It appears the bad commit is the one Fisheye created when I imported the repository:

fisheye-bad-commit.PNG

[Conor · Accepted solution]

Dave,

Sorry. The initial import commit is a synthetic commit created to capture the state of the repository at the point of the initial import. It's date is set to the epoch date because it needs to have a value and this value should keep it out of the way of the real commits in the repository. 

Does this cause a problem?

[Dave]

Well sure its a problem. It throws of the line history, commit stats, and numerous reports as well. I would certainly consider this a bug. Is there a work-around to change the date on that synthetic commit in the database?

[Dave]

Created an issue for this: https://jira.atlassian.com/browse/FE-5378

[Nick]

Hi, we have the exact same garbage, do not worry you're not alone :)

Скриншот 2014-10-22 19.30.57.png

[Conor]

It would seem that some of your commits do not have dates and FishEye applies the Java "epoch" date which is 1-Jan-1970. I guess this is then being time zone adjusted into 1969.

Can you check the commit that is showing up in that time region and then have a look at it in Subversion to see why it might not have a date.

[Dave]

The bad commit was a "fake" commit created by Fisheye when it did the import - I attached the screenshot to my question.