Bug 8159 - Error retrieving history
Summary: Error retrieving history
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Version Control ()
Version: 4.0
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Alan McGovern
Depends on:
Reported: 2012-11-01 19:26 UTC by Mikayla Hutchinson [MSFT]
Modified: 2012-11-14 08:48 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Mikayla Hutchinson [MSFT] 2012-11-01 19:26:46 UTC
ERROR [2012-11-01 18:42:07Z]: Error retrieving history
System.ArgumentException: E-mail address of PersonIdent must not be null.
  at NGit.PersonIdent..ctor (System.String aName, System.String aEmailAddress, Int64 aWhen, Int32 aTZ) [0x00000] in <filename unknown>:0 
  at NGit.PersonIdent..ctor (System.String aName, System.String aEmailAddress, Int64 when) [0x00000] in <filename unknown>:0 
  at NGit.PersonIdent..ctor (System.String aName, System.String aEmailAddress) [0x00000] in <filename unknown>:0 
  at NGit.Blame.Candidate+BlobCandidate.GetAuthor () [0x00000] in <filename unknown>:0 
  at NGit.Blame.BlameGenerator.GetSourceAuthor () [0x00000] in <filename unknown>:0 
  at NGit.Blame.BlameResult.LoadFrom (NGit.Blame.BlameGenerator gen) [0x00000] in <filename unknown>:0 
  at NGit.Blame.BlameResult.ComputeAll () [0x00000] in <filename unknown>:0 
  at NGit.Blame.BlameGenerator.ComputeBlameResult () [0x00000] in <filename unknown>:0 
  at NGit.Api.BlameCommand.Call () [0x00000] in <filename unknown>:0 
  at MonoDevelop.VersionControl.Git.GitRepository.GetAnnotations (FilePath repositoryPath) [0x00000] in <filename unknown>:0 
  at MonoDevelop.VersionControl.Views.BlameWidget+BlameRenderer+<UpdateAnnotations>c__AnonStorey12.<>m__40 (System.Object ) [0x00000] in <filename unknown>:0
Comment 1 Alan McGovern 2012-11-06 09:09:45 UTC
How did you trigger this? It looks like you have a null email but I don't know what would trigger it.
Comment 2 Alan McGovern 2012-11-06 09:21:09 UTC
Hrmm. This is weird. It looks like this error is guaranteed to happen if someone invokes BlobCandidate.GetAuthor (). This method invokes the PersonIdent ctor passing a null value for the email address. The email address is then null checked and an exception is thrown. It could be a jgit conversion error, or it could just be a bug in jgit. Did this happen before or after the most recent jgit bump?
Comment 3 Mikayla Hutchinson [MSFT] 2012-11-06 11:48:21 UTC
It happened immediately before I filed it, with a fresh build IIRC.
Comment 4 Alan McGovern 2012-11-06 19:58:00 UTC
Jeremie was demoing an issue to me on his desktop and he hit this exact issue. I opened the same file on my system and did not. I honestly have no idea what is causing this, but someone experiencing the issue is going to have to debug this because I am unaffected by it. I also won't have access to his desktop for at least a week.
Comment 5 Alan McGovern 2012-11-14 08:48:57 UTC
Fixed in git. It was a jgit regression which was fixed several commits after I updated ngit.