"$ git init; ti init; ti" firing bugs with any command, no error-handling with null -repo about ticgit

[jeffWelling]

This has been dealt with in the latest version, though it does seem like an edge case. Please update your gem and check that this issue is resolved for you.

The issue that I fixed for this (it wasn't 100% clear to me what your problem was) was that TicGit-ng didn't check for and gracefully fail when someone tried to use TicGit-ng with a repository that did not have any commits in it yet. To resolve this, I added error checking for this condition and an rspec spec to prevent regression, so if I understood your problem correctly then hopefully this is resolved.

Let me know, in the meantime I will mark this issue as closed.

[heoa]

I am using now Debian and some errors, not sure whether I am running the newest ticgit.

$ cat /proc/version
Linux version 3.2.0-0.bpo.2-686-pae (Debian 3.2.20-1~bpo60+1) ([email protected]) (gcc version 4.4.5 (Debian 4.4.5-8) ) #1 SMP Sat Jun 30 08:29:17 UTC 2012
$ git init
$ ti init
/usr/lib/ruby/1.8/git/lib.rb:643:in command': git branch -a 2>&1:fatal: Failed to resolve HEAD as a valid ref. (Git::GitExecuteError) from /usr/lib/ruby/1.8/git/lib.rb:615:incommand_lines'
from /usr/lib/ruby/1.8/git/lib.rb:209:in branches_all' from /usr/lib/ruby/1.8/ticgit/base.rb:241:inload_tickets'
from /usr/lib/ruby/1.8/ticgit/base.rb:72:in reset_ticgit' from /usr/lib/ruby/1.8/ticgit/base.rb:38:ininitialize'
from /usr/lib/ruby/1.8/ticgit.rb:25:in new' from /usr/lib/ruby/1.8/ticgit.rb:25:inopen'
from /usr/lib/ruby/1.8/ticgit/cli.rb:23:in initialize' from /usr/lib/ruby/1.8/ticgit/cli.rb:16:innew'
from /usr/lib/ruby/1.8/ticgit/cli.rb:16:in parse' from /usr/lib/ruby/1.8/ticgit/cli.rb:12:inexecute'
from /usr/bin/ti:10
$ ti
/usr/lib/ruby/1.8/git/lib.rb:643:in command': git branch -a 2>&1:fatal: Failed to resolve HEAD as a valid ref. (Git::GitExecuteError) from /usr/lib/ruby/1.8/git/lib.rb:615:incommand_lines'
from /usr/lib/ruby/1.8/git/lib.rb:209:in branches_all' from /usr/lib/ruby/1.8/ticgit/base.rb:241:inload_tickets'
from /usr/lib/ruby/1.8/ticgit/base.rb:72:in reset_ticgit' from /usr/lib/ruby/1.8/ticgit/base.rb:38:ininitialize'
from /usr/lib/ruby/1.8/ticgit.rb:25:in new' from /usr/lib/ruby/1.8/ticgit.rb:25:inopen'
from /usr/lib/ruby/1.8/ticgit/cli.rb:23:in initialize' from /usr/lib/ruby/1.8/ticgit/cli.rb:16:innew'
from /usr/lib/ruby/1.8/ticgit/cli.rb:16:in parse' from /usr/lib/ruby/1.8/ticgit/cli.rb:12:inexecute'
from /usr/bin/ti:10
$ dpkg -l ticgit
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==========================-==========================-====================================================================
ii ticgit 0.3.3-2 ticketing system built on Git

[jeffWelling]

1. That's improper usage for TicGit-ng. The appropriate usage is to first add at least one commit to git, and in the latest version of TicGit-ng there has been code added to make sure that when you try to use TicGit-ng without adding commits to git first that TicGit-ng fails gracefully and explains why it has failed.

2. It appears you are using TicGit, not TicGit-ng, and should be filing these issues on the TicGit page instead of the TicGit-ng Issues page.