The Accidental Rubyist

invalid byte sequence in UTF-8

Getting ruby Tracker to work

with 3 comments

I had tried out Tracker recently (a simple bug tracker using sqlite as a backend). Gave errors, and the author reported that it had been a long time
and then he went silent. Today, made a few corrections and its working.
However, it is *very slow*. Each command takes a few seconds to respond. I am on 1.9.

I added require acts_as_list in environment.rb. You will need to install this gem in addition to active_record.

2 files contain :with_scope which is now protected.
Corrected as per Now all the actions mentioned on the rubyforge page are working.

In the meantime, I had got ditz to work in ruby 1.9 but with *some errors* (using someones fork). So i am not
too keen on it, although i might start using it later. So i have adapted todo.txt (a cute shell script todo list manager) to create bug files. However, using flat files in email header format does limit the ability to do searches for multiple keys. Its like reinventing the wheel with multiple greps. Much better to use sql instead.

todo.txt is great for todo’s but only stores a line per todo, no comments, fixes etc so it can’t be used for tracking bugs. I really should redo this shell-script based bug tracker using ruby thor and highline.


Written by totalrecall

November 8, 2009 at 10:22 am

Posted in ruby

3 Responses

Subscribe to comments with RSS.

  1. Thanks a lot for those helpful hints 🙂 I’ve contacted the author of Tracker and haven’t got any response yet, so I’m glad I found your entry. Did you eventually create some commandline issue tracker as you planned or did you find something else?


    March 27, 2011 at 12:57 am

  2. I did create a bash shell and then ruby commandline program called bugzy. However, i have not used it much so don’t recommend them. You can try them out if you want. It’s on my github account (link on right side)


    March 27, 2011 at 10:37 am

  3. Ah thanks 🙂 (Somehow I missed the follow-up notification, hence the late answer). I’ll definitely take a closer look at bugzy. Cheers.


    March 29, 2011 at 3:21 pm

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: