Bugfix: Hobo 0.6.4

Posted almost 7 years back at The Hobo Blog

As warned of in the previous post, we had some Prototype/Scriptaculous related problems in 0.6.3. Now fixed in Hobo 0.6.4.

Same deal as usual:

Bugfix: Hobo 0.6.4

Posted almost 7 years back at The Hobo Blog

As warned of in the previous post, we had some Prototype/Scriptaculous related problems in 0.6.3. Now fixed in Hobo 0.6.4.

Same deal as usual:

0.6.3 - Following up

Posted almost 7 years back at The Hobo Blog

Oops – forgot to mention that Hobo 0.6.3 requires Rails 2.0 RC1

To freeze:

rake rails:freeze:edge TAG=rel_2-0-0_RC1

If you want to use the hobo command, or if you don’t like freezing Rails, you’ll need the 2.0RC1 gems:

gem update rails --source http://gems.rubyonrails.org -y

Also note that Hobo 0.6.3 has a new version of lowpro.js that needs Prototype 1.6 (Rails is on Prototype 1.6 now). You might need a

rake rails:update:javascripts

There may be a few bugs related to the switch to Prototype 1.6. These can slip through because most of our tests are in applications that have not been upgraded to Prototype 1.6 yet. Stay tuned.

0.6.3 - Following up

Posted almost 7 years back at The Hobo Blog

Oops – forgot to mention that Hobo 0.6.3 requires Rails 2.0 RC1

To freeze:

rake rails:freeze:edge TAG=rel_2-0-0_RC1

If you want to use the hobo command, or if you don’t like freezing Rails, you’ll need the 2.0RC1 gems:

gem update rails --source http://gems.rubyonrails.org -y

Also note that Hobo 0.6.3 has a new version of lowpro.js that needs Prototype 1.6 (Rails is on Prototype 1.6 now). You might need a

rake rails:update:javascripts

There may be a few bugs related to the switch to Prototype 1.6. These can slip through because most of our tests are in applications that have not been upgraded to Prototype 1.6 yet. Stay tuned.

De-ASCII Your Rails Logs

Posted almost 7 years back at Alloy Code - Home

Recently, I've been delving into some filter-related problems in one of my Rails applications. This has required me to trap and review specific segments of my Rails log files. As part of my initial stack setup when I begin a new project, I install the Query Analyzer and Query Trace plugins.

The upside is I get very detailed trace information for my application, pictured below:

Log output

The downside is, when these files are viewed with Textmate or Console, they wind up looking more like this:

    Rendered events/_event (0.00036)  
      [4;35;1mSlot Load (0.000361)   SELECT * FROM 'slots' WHERE (slots.event_id = 23)   
        [35;2mvendor/plugins/query_analyzer/lib/query_analyzer.rb:38:in 'select'  
        [35;2mlib/association_extensions/chronological.rb:9:in 'first'  
        [35;2mapp/models/event.rb:109:in 'begin_at'  
        [35;2mapp/views/events/_event.html.erb:6:in '_run_erb_47app47views47events47_event46html46erb'  
        [35;2mapp/views/events/index.html.erb:39:in '_run_erb_47app47views47events47index46html46erb'

Today's "stretch the brain" exercise centered around creating a Textmate command to clear out this unnecessary cruft. For starters, I cloned the Text bundle's "Remove Unprintable Characters in Document / Selection" command. It looks like the Textmate folks are using Perl to remove unprintable characters:

perl -pe 's/[^\t\n\x20-\xFF]|\x7F|\xC2[\x80-\x9F]//g'

I left all the settings unchanged:
Save: Nothing
Input: Selected Text or Document
Output: Replace Selected Text

And edited the Perl regular expression to match each of the three possible variants of ASCII instruction:

perl -pe 's/\[\d;?(\d+)?;?(\d)?m//g'

Success! Now, with one keystroke, I can remove all that extra information from my log file, and get down to business.

De-ASCII Your Rails Logs

Posted almost 7 years back at Alloy Code - Home

Recently, I've been delving into some filter-related problems in one of my Rails applications. This has required me to trap and review specific segments of my Rails log files. As part of my initial stack setup when I begin a new project, I install the Query Analyzer and Query Trace plugins.

The upside is I get very detailed trace information for my application, pictured below:

Log output

The downside is, when these files are viewed with Textmate or Console, they wind up looking more like this:

    Rendered events/_event (0.00036)  
      [4;35;1mSlot Load (0.000361)   SELECT * FROM 'slots' WHERE (slots.event_id = 23)   
        [35;2mvendor/plugins/query_analyzer/lib/query_analyzer.rb:38:in 'select'  
        [35;2mlib/association_extensions/chronological.rb:9:in 'first'  
        [35;2mapp/models/event.rb:109:in 'begin_at'  
        [35;2mapp/views/events/_event.html.erb:6:in '_run_erb_47app47views47events47_event46html46erb'  
        [35;2mapp/views/events/index.html.erb:39:in '_run_erb_47app47views47events47index46html46erb'

Today's "stretch the brain" exercise centered around creating a Textmate command to clear out this unnecessary cruft. For starters, I cloned the Text bundle's "Remove Unprintable Characters in Document / Selection" command. It looks like the Textmate folks are using Perl to remove unprintable characters:

perl -pe 's/[^\t\n\x20-\xFF]|\x7F|\xC2[\x80-\x9F]//g'

I left all the settings unchanged:
Save: Nothing
Input: Selected Text or Document
Output: Replace Selected Text

And edited the Perl regular expression to match each of the three possible variants of ASCII instruction:

perl -pe 's/\[\d;?(\d+)?;?(\d)?m//g'

Success! Now, with one keystroke, I can remove all that extra information from my log file, and get down to business.

Hobo 0.6.3 released

Posted almost 7 years back at The Hobo Blog

OK finally got it out there. Hobo 0.6.3 is mainly a whole load of small improvements. There are many breaking changes as always. Here’s a quick heads up on some things to watch out for:

  • The page templates in rapid-pages have been improved a lot. If you use them you should study the new templates carefully to see how you need to update your own code.

  • If you were using the multiple-object create/update features in Hobo’s controller, I’m afraid that feature has been deemed lame and is gone.

And a couple of teeny ones:

  • We no longer support the shortcut hobo_user_model :email. You need to explicitly call set_login_attr :email. You should do this after the fields declaration.

  • The css class button_input is now just button, which may mess with your beautiful design a tad.

There’s a ton of other changes but those are my list of “things to mention in the blog post”.

Go get it:

Now I just have one little feature I need to implement and I can get stuck in to the … drum-roll … documentation!

Hobo 0.6.3 released

Posted almost 7 years back at The Hobo Blog

OK finally got it out there. Hobo 0.6.3 is mainly a whole load of small improvements. There are many breaking changes as always. Here’s a quick heads up on some things to watch out for:

  • The page templates in rapid-pages have been improved a lot. If you use them you should study the new templates carefully to see how you need to update your own code.

  • If you were using the multiple-object create/update features in Hobo’s controller, I’m afraid that feature has been deemed lame and is gone.

And a couple of teeny ones:

  • We no longer support the shortcut hobo_user_model :email. You need to explicitly call set_login_attr :email. You should do this after the fields declaration.

  • The css class button_input is now just button, which may mess with your beautiful design a tad.

There’s a ton of other changes but those are my list of “things to mention in the blog post”.

Go get it:

Now I just have one little feature I need to implement and I can get stuck in to the … drum-roll … documentation!

De-ASCII Your Rails Logs

Posted almost 7 years back at Alloy Code - Home

Recently, I've been delving into some filter-related problems in one of my Rails applications. This has required me to trap and review specific segments of my Rails log files. As part of my initial stack setup when I begin a new project, I install the Query Analyzer and Query Trace plugins.

The upside is I get very detailed trace information for my application, pictured below:

Log output

The downside is, when these files are viewed with Textmate or Console, they wind up looking more like this:

    Rendered events/_event (0.00036)  
      [4;35;1mSlot Load (0.000361)   SELECT * FROM 'slots' WHERE (slots.event_id = 23)   
        [35;2mvendor/plugins/query_analyzer/lib/query_analyzer.rb:38:in 'select'  
        [35;2mlib/association_extensions/chronological.rb:9:in 'first'  
        [35;2mapp/models/event.rb:109:in 'begin_at'  
        [35;2mapp/views/events/_event.html.erb:6:in '_run_erb_47app47views47events47_event46html46erb'  
        [35;2mapp/views/events/index.html.erb:39:in '_run_erb_47app47views47events47index46html46erb'

Today's "stretch the brain" exercise centered around creating a Textmate command to clear out this unnecessary cruft. For starters, I cloned the Text bundle's "Remove Unprintable Characters in Document / Selection" command. It looks like the Textmate folks are using Perl to remove unprintable characters:

perl -pe 's/[^\t\n\x20-\xFF]|\x7F|\xC2[\x80-\x9F]//g'

I left all the settings unchanged:
Save: Nothing
Input: Selected Text or Document
Output: Replace Selected Text

And edited the Perl regular expression to match each of the three possible variants of ASCII instruction:

perl -pe 's/\[\d;?(\d+)?;?(\d)?m//g'

Success! Now, with one keystroke, I can remove all that extra information from my log file, and get down to business.

De-ASCII Your Rails Logs

Posted almost 7 years back at Alloy Code - Home

Recently, I've been delving into some filter-related problems in one of my Rails applications. This has required me to trap and review specific segments of my Rails log files. As part of my initial stack setup when I begin a new project, I install the Query Analyzer and Query Trace plugins.

The upside is I get very detailed trace information for my application, pictured below:

Log output

The downside is, when these files are viewed with Textmate or Console, they wind up looking more like this:

    Rendered events/_event (0.00036)  
      [4;35;1mSlot Load (0.000361)   SELECT * FROM 'slots' WHERE (slots.event_id = 23)   
        [35;2mvendor/plugins/query_analyzer/lib/query_analyzer.rb:38:in 'select'  
        [35;2mlib/association_extensions/chronological.rb:9:in 'first'  
        [35;2mapp/models/event.rb:109:in 'begin_at'  
        [35;2mapp/views/events/_event.html.erb:6:in '_run_erb_47app47views47events47_event46html46erb'  
        [35;2mapp/views/events/index.html.erb:39:in '_run_erb_47app47views47events47index46html46erb'

Today's "stretch the brain" exercise centered around creating a Textmate command to clear out this unnecessary cruft. For starters, I cloned the Text bundle's "Remove Unprintable Characters in Document / Selection" command. It looks like the Textmate folks are using Perl to remove unprintable characters:

perl -pe 's/[^\t\n\x20-\xFF]|\x7F|\xC2[\x80-\x9F]//g'

I left all the settings unchanged:
Save: Nothing
Input: Selected Text or Document
Output: Replace Selected Text

And edited the Perl regular expression to match each of the three possible variants of ASCII instruction:

perl -pe 's/\[\d;?(\d+)?;?(\d)?m//g'

Success! Now, with one keystroke, I can remove all that extra information from my log file, and get down to business.

Rackspace trouble knocks 37signals offline [back!]

Posted almost 7 years back at Loud Thinking

Rackspace has had a major power incident at the data center keeping the 37signals suite of machines. Apparently, a traffic accident knocked power out to some vital cooling systems. When the power was restored through generators, the cooling systems failed to come back online.

They now have the cooling systems back up and are getting everything back online. We hope to be back very shortly.

No data has been harmed, the machines were preemptively shut down when the cooling systems failed.

A good number of other applications, such as Wesabe was hit by this as well. Hopefully they'll be back shortly as well.

UPDATE: Everything is back in working order. Read more on the product blog.

Rackspace trouble knocks 37signals offline [back!]

Posted almost 7 years back at Loud Thinking

Rackspace has had a major power incident at the data center keeping the 37signals suite of machines. Apparently, a traffic accident knocked power out to some vital cooling systems. When the power was restored through generators, the cooling systems failed to come back online.

They now have the cooling systems back up and are getting everything back online. We hope to be back very shortly.

No data has been harmed, the machines were preemptively shut down when the cooling systems failed.

A good number of other applications, such as Wesabe was hit by this as well. Hopefully they'll be back shortly as well.

UPDATE: Everything is back in working order. Read more on the product blog.

Digital Comics, Unlimited

Posted almost 7 years back at zerosum dirt(nap) - Home

I’m not ashamed to admit that I’m a bit of a comic book geek.

When I was a kid, I was a hardcore fanboy who spent pretty nearly all his paper route money on weekly trips to the local comic shop in Dover. I have no apology for that. As a technology geek also, I’ve built a social comic book pull list organizer that has yet to officially launch (we’re looking for someone who’s excited about comics and community building, no techie skills required, email me if you’re interested!) and I’ve done a little ancillary plugin work for the geeky folks over at Heavy Ink too.

These days I buy mostly graphic novels, but I’ve always loved the feel of a floppy, and back when I used to buy titles monthly, there was just something unspeakably awesome about ‘new comic book day’ and the excitement of pouring through the stacks in a local shop looking for that one key back issue…

Like most fans, I have mixed feelings about the digitization of comics. On one hand, I’d probably read a lot more of them if they were available (ahem, legally of course) through a cheap, easy to use digital distribution service like iTunes. On the other hand, I’m sort of glad this hasn’t happened, because it would kill a lot of the allure of it for me if the comics on paper were to become a thing of the past.

I imagine I’m not the only one who was both excited and, at the same time, just a little tiny bit bummed about the announcement of Marvel Comics Unlimited yesterday (NOTE: as of right now the site appears to be down for maintenance, coming soon). The basic premise is that Marvel will offer an online archive of over 2500 back issues online in high-resolution format, starting at about $5/mo. They’re also making a free sampler of 250 titles available to wet your appetites.

Marvel’s hedging their bets a little though, which is smart. New issues won’t appear on the Marvel Unlimited site until six months after their initial print publication. This is great for those of us who read graphic novels, and aren’t used to picking up books every week anyway, and it keeps the floppies in circulation. After a bit of consternation, I’ve decided that it’s pretty much a win/win. Of course, as it always is on the web, the user experience will determine the ultimate success or failure of the venture. The flash-based digital comics I’ve seen from Marvel up to this point haven’t exactly been the most pleasant things to read, so here’s to hoping this is an entirely new interface to the library.

Anyway, I’m looking forward to reading more about this, both as a comic book enthusiast and as a technologist. Welcome to the 21st century, comic fans. For better or for worse.

It’s about time, I guess!

Turn On Your Buzzword Filter

Posted almost 7 years back at zerosum dirt(nap) - Home

BigLove [12:37am]: my eyes crossed from all the buzzwords zapnap
zapnap [12:38am]: turn on your buzzword filter. OMFG WHERE DID T EH INTERNETS GO?

Episode 79: Generate Named Routes

Posted almost 7 years back at Railscasts

This more advanced episode will show you how to dynamically generate named routes by adding a method to the map object.