Added unit test to demonstrate parsing bug

[haacked]

Added a unit test to demonstrate a commit parsing bug that still exists.

LibGit2Sharp.LibGit2SharpException : An error was raised by libgit2.
Class = Odb (-1).
Failed to parse commit 54a169f6bcf7afdb4bbcd9517944b933422b9a92 -
cannot parse commit time...

[mfecteau]

Any idea when this will be released?

[nulltoken]

The fix has been merged in libgit2 on July, 12th.

LibGit2Sharp vNext branch will be updated with a new version of libgit2 before July, 22nd.

[nulltoken]

Thanks for the report. Fixed in vNext.

[mfecteau]

That didn't fix the issue. I have responded to the last email I received and have attached TheLog.txt to that email.

[nulltoken]

@mfecteau I'm sorry, I'm not sure I understand what TheLog.txt refers to. Could you please give us more context?

That didn't fix the issue.

@haacked should this issue be reopened?

[mfecteau]

I was told, to follow an ongoing issue I had with the program shutting down every time it opens to go here. I was also told a fix for this issue would be released July 22. In any case I downloaded the latest from the web a couple of days ago and the issue remains. The program opens for a few seconds (up to 30 or so) and whether a click on anything or not the program shuts down. The comment about sending TheLog.txt in a separate email was just FYI. I thought this discussion would have access to that email trail. I replied to a previous email trail at "[email protected]", that's where I sent TheLog.txt.

[uluhonolulu]

@mfecteau LibGit2Sharp is not a program, it doesn't open, and cannot be shutting down. It also doesn't produce logs. Looks like you're talking about something different.

[nulltoken]

@mfecteau Wow, thanks a lot for this very detailed information! This is the bug tracker for the LibGit2Sharp, one of the components that GitHub for Windows depends on.

I know that the team behind GHfW is pretty efficient. Now that the bug that was bothering you has been fixed in LibGit2Sharp, a new version of GHfW should be released soon or someone from the support will reach out to you in order to keep you updated.

[haacked]

@mfecteau Yeah, I'm not sure we've incorporated this bug fix in yet. But we'll get to it soon.