This image was taken in Hawaii on our honeymoon. Unfortunately this article doesn’t paint a flattering picture of the big meatball company.
Author: matte
Microfiber humor at CostCo
Pregame CalTrain drinker
At the game
I recently started playing around with the log_buddy gem for Rails and because my development machine is on windows, the “d” method wasn’t playing nice with some paths. it didn’t like paths that included the drive letter.
this is a sample of a line that would cause log_buddy to barf. it just so happens to also be the line that causes the error. 🙂
c:/ruby/lib/ruby/gems/1.8/gems/log_buddy-0.0.5/lib/log_buddy.rb:98:in `read_line'
the original line looked like this…
file, line_number = frame.split(/:/, 2)
the fix is to replace that line with
file, line_number = frame.reverse.split(/:/, 3)[1..2].map(&:reverse).reverse
yeah. ugly, and maybe could be written better but it works for me.
now if only I could get log_buddy to output good inspections of objects I toss to it… like “current_user”. I’m prolly using it wrong right now, but this isn’t helpful…
current_user = '#<User:0x47143d8>'
just saying. 🙂
UPDATE: I monkeypatched log_buddy to fix this functionality. I created a “RAILS_ROOT/lib/log_buddy_extensions.rb” file with the following code.
class LogBuddy
private
# Return the calling line
def self.read_line(frame)
file, line_number = frame.reverse.split(/:/, 3)[1..2].map(&:reverse).reverse
line_number = line_number.to_i
lines = File.readlines(file)
lines[line_number - 1]
end
end
and I figured out that the “current_user” line above shouldn’t be …
d { current_user }
it should be
d { current_user.inspect }
that outputs what I want …
current_user.inspect = '#<User id: 1, login: "matte", email: "matte@localhost", crypted_password: "...", salt: "...", created_at: "2007-08-30 18:23:32", updated_at: "2008-07-08 18:57:45", remember_token: "...", remember_token_expires_at: "2008-07-22 18:57:45", name: "...", password_reset_code: nil, company_id: 2, active: true>'
To say that this TOTALLY made my weekend would be one of the biggest understatements EVER!!!! In the back of my mind I just knew they had to be working on the successor to my favorite video game ever but it never pushed far enough forward for me to dive into the Intertubes to see if any rumors were swirling of it’s successor. Well, it’s finally been announced. Diablo 3 is on it’s way… sometime. As usual Blizzard is taking their sweet little time getting it right, and I applaud them for that. I can wait. I’m a patient man. After that though, Cathy isn’t going to see me for weeks. 🙂
This was an extremely productive weekend as well, despite my head not being 100% into what I was doing due to a certain video game announcement. But I rewired the house phone lines, installed two new wall jacks for the phone and cable in the two offices and Cath and I installed a new foyer ceiling light. I surprised her with the hallway light replacement last night.
The handyman part of me is finally able to come out and play. I even got to kill many many many ants last night that had all gotten together and made a decision to enjoy the cat food in our kitchen. Well, Cath took care of the inside ants while I drove home and then killed EVERY SINGLE ANT ON OUR OUR PROPERTY. Including two queens.
Now… where was that Diablo 2 disc…








