crash - stack trace about bugspots

[igrigorik]

This looks like a bug in grit library, which is used to read out the git commit info.

mojombo/grit#57

Are you trying to read an empty directory, or git repo with no commits by any chance?

[sawilde]

The repo has lots of commits (it is my opencover project) and the directory is not empty. It may have sub directories which are empty though - would that cause problems?

[igrigorik]

I hope not! It's probably worth opening a bug on the grit repo around this.. If you're familiar with ruby, can you try dropping into irb and try to open the repo, walk over the commits?

https://github.com/mojombo/grit - check out examples in the readme, or take a look at the source in bugspots (which is very, very simple)

[msgerbush]

Not exactly sure what is going on here, but it looks like some of the arguments getting passed to git-log when commit.stats is called are getting messed up. Its hard to tell without being able to reproduce the error. This is definitely a grit issue, but this grit stack trace includes code that is over a year old and has been completely refactored. You might want to try just updating your version of grit and seeing if that fixes the issue.

[swang]

Hello,

I got this error not because of the issue #41 in grit, but because grit does not work properly in Windows. Windows separates paths in its environment variable by using semi-colons rather than colons and grit only tokenized on colons. I was going to submit a patch but someone beat me to the punch.

mojombo/grit#75

So what I did was run:

git clone https://github.com/Ziaw/grit.git
cd grit
git checkout -b patch-1 origin/patch-1
gem build grit

Then I uninstalled grit and reinstalled the built gem in the folder

Once I did that I was able to run bugspots fine.