Rule #1: There are no rules.

μProject: Resque-backtrace

| Comments

I was trying to debug a Resque job recently and I was actually quite surprised to find that it didn’t print backtraces on exceptions. Now, in production you’re definitely going to using an exception tracker like Honeybadger or AirBrake, but you probably won’t be doing so in development, so there’s nowhere at all to view backtraces when things go wrong. I threw together a tiny gem to dump them to the console like you’d expect: resque-backtrace.