-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash when counting commits in multiple repos #47
Comments
It looks like you only have 2 bots in TTC_BOTS -- i think that's where the slice is failing, maybe. Might adding a third? |
I also tried with the default TTC_BOTS and an empty value. As mentioned, only the TTC_REPOS variable affects this issue. |
I really can't repro this, nor have heard of anyone else having problems in this way :( |
Then I'm happy for everyone else 👍 I'll leave this open and try to debug myself. |
As of version |
The problem resolved on its own recently. Hard to find out afterwards what the real reason was (such as the state of my 200+ Git repos)... 1.2.0 is also working fine for me. We can close this and hope it doesn't happen anymore ;) Thanks! |
I'm also getting this error, and it's caused by a specific one of my git repos, it seems. 😢 |
@jarednorman I've noticed I couldn't use a git repo with a dot in the name. Maybe it's that? :( |
No dot or any other weird characters. It's just of the format "fooBar". |
@notwaldorf Is this a git-log or an git-standup issue? I think this should be fixed! |
Changing between git-log/git-standup has no effect on the error for me. The only thing that changes whether I get this error is whether I include this one repo I have in TTC_REPOS. |
Mysteriously just started working today. 😖 |
I had the same problem, and traced it to curly braces in the commit messages wreaking havoc with the "tag parser" implemented in the blessed library. The simplest fix is to set |
I also had this problem with just one repo, which had curly braces in commit messages. I applied @cfinucane's patch and it works. 😀 |
Having the same issue:
Probably also due to commits titled like
For me it was also "fixed" by changing the @AndiDog Would you reopen and apply @cfinucane 's patch? :) |
I won't find the time in the near future to work on this issue. Maybe somebody can create a pull-request? It shouldn't be that hard. 🤞 |
Node Version:
v7.2.1
tiny-core-terminal version:
1.0.8
Shell: bash
Terminal Program: iTerm2
Operating System: macOS
I have quite a few repos in
~/dev
. The dashboard starts up, starts counting commits for a second and then crashes. UsingTTC_REPOS=/single/repo
works fine for the ones I tried. Didn't try very hard to debug into the blessed library since I don't know what the code is doing. What I can tell you that at that given code location in blessed (/usr/local/lib/node_modules/tiny-care-terminal/node_modules/blessed/lib/program.js:2543
), we havepart == "cpp"
andval == "cpp"
.Unsetting env vars other than TTC_REPOS doesn't make a difference.
The text was updated successfully, but these errors were encountered: