By now I think everyone agrees that Pry is the best thing to happen to the Rails console since...well, ever. Built-in to pry are a few really cool features that make it much easier to work with exceptions than it was in plain old IRB. Let's take a look.
In this post we look at Ruby's exception class heirarchy, and how you can use it to be as broad or as narrow as you like when rescuing exceptions.
Exceptions are classes, just like everything else in Ruby. This post will show you how to create your own custom exceptions without falling into some common traps that snare beginners.
tl;dr If you want to run a shell command from Ruby and capture its stdout, stderr and return status, check out the
Open3.capture3 method. If you'd like to process stdout and stderr data in a streaming fashion, check out
Never rescue Exception in Ruby! - Maybe you've heard this before. It's good advice, but it's pretty confusing unless you're already in the know. Let's break this statement down and see what it means.
Gem installs can be slooow. One of the biggest culprits is documentation. Every time you install a gem, your computer has to scan the source of that gem and generate documentation.
Have you ever wished you could use honeybadger on your iPhone, iPad or Apple Watch? Well now you can.
Honeybadger has integrated tightly with GitHub since we started, allowing you to jump directly to the bug in your source code and automatically managing issues for errors. Today I'm happy to announce that we're bringing all the features our GitHub users know and love to Bitbucket -- because, let's face it: Bitbucket doesn't get enough love.
Everyone is talking about Ruby performance lately, and with good reason. It turns out that with some smallish tweaks to your code it's possible to increase performance by up to 99.9%.
Last week we sent out a survey to our users asking them what changes they would make to Honeybadger. We're planning on redesigning the user interface and wanted some feedback.
After nearly six months of effort that nearly cost us the sanity of our beloved Joshua Wood, we are proud to officially announce the release of version 2.x of the Honeybadger gem. Upgrade instructions are here.
When your site is totally unresponsive (i.e. down), it's a big deal. Oddly enough, application errors may not surface during major outages if the failure is outside of the application. That's why we built uptime monitoring into Honeybadger: in addition to monitoring your app for internal exceptions, we also ping external endpoints from multiple locations around the world to make sure it's online and responding as expected. When your site is down we can notify you via email, SMS, Slack, or any of our other myriad notification options.
Here at Honeybadger, we have a lot of data, which presents us with a few problems. One of the biggest challenges is data culling. Removing old data that nobody uses any more, while keeping the good stuff.
SVG has been around since 1999. Those were heady days. People had invented and were in love with XML - if you can believe that. If you picked up a trade magazine like Dr. Dobb's Journal - which in those days both existed and was printed on real paper - you saw how every single problem in computer science was being solved via the magic of XML.
We recently moved our blog to WordPress. And though WP seems to be the best blogging platform around, it's not exactly fast. Scratch that. It's slow. It's really slow.
If you use Honeybadger, you may have come across "tags" in the UI. Tags are the key that unlocks a lot of advanced functionality in Honeybadger.
Today we're releasing a powerful new set of search features not only to help you find errors inside of Honeybadger, but to tell Honeybadger which errors you want to be notified of.
Our latest feature saves you a click or two — and you're going to love it. You probably already know that Honeybadger can let you know which users were impacted by an error in your Rails application. By using the context feature you can send custom data, such as a user id and a user email address, along with the other application data that's automatically sent with each error report. I use this all the time to quickly email people to let them know that the error they just encountered at my site has already been fixed. They love that. :)
Today we're announcing the launch of a fun feature: In-browser notifications. Once enabled on the Notifications tab of the Project Settings page, you'll get a popup notification in the corner of the browser window when one of the events occurs that you've selected to be alerted about (like an error occurring, or a comment being added). As an added bonus, you can also choose to have a popup window appear on your desktop. The combination of Pusher and pNotify made this easy to implement -- here's how I did it.
LessAccounting has been in production since 2007 and it was started in Ruby 1.8.6 and Rails 2. Yeah, it’s been around for a while.