honeybadger 1.6.1 → 1.6.2

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 432a8044719792bb87fa036981d18363c02407b1
+  data.tar.gz: 21a0664d989f278e520867dd4651d2c6c8577099
+SHA512:
+  metadata.gz: dbfa579b6f06989fbadbf4855b46232bea1b9c65822cdcac5387b803b72549b8a5e1650e6d41e2680b1644e791af9a0a6ac9096d9af4c8284837e8c7c31ce6cb
+  data.tar.gz: f39e364b00a9ad3ecc354fdb0faf74901406947f311f6f974489e6193f5c6a7e5ba8bdb761580bf9ca7a759fdd49aeddb75a37da2e464d440dd0b8e81258f324

data/CHANGELOG.md

@@ -1,7 +1,8 @@
 ## Honeybadger 1.7.0 (Unreleased) ##
 
-* Added a deploy rake task which always loads the Rails environment.
-  Also added ability to override rake task in Capistrano recipe.
+## Honeybadger 1.6.2 ##
+
+* Fail gracefully when Rack params cannot be parsed
 
   *Joshua Wood*
 
@@ -11,6 +12,11 @@
 
   *Joshua Wood*
 
+* Added a deploy rake task which always loads the Rails environment.
+  Also added ability to override rake task in Capistrano recipe.
+
+  *Joshua Wood*
+
 ## Honeybadger 1.6.0 ##
 
 * Rescue from load error when application_controller.rb is missing.

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    honeybadger (1.6.1)
+    honeybadger (1.6.2)
       json
 
 GEM

data/README.md

@@ -13,32 +13,40 @@ to the Honeybadger server specified in your environment.
 
 Add the Honeybadger gem to your gemfile:
 
-    gem 'honeybadger'
+```ruby
+gem 'honeybadger'
+```
 
 Then generate the initializer:
 
     rails generate honeybadger --api-key <Your Api Key>
 
 If you prefer to manually create the initializer, that's simple enough.
-Just put the code below in config/initializers/honeybadger.rb
+Just put the code below in `config/initializers/honeybadger.rb`
 
-    Honeybadger.configure do |config|
-      config.api_key = '[your-api-key]'
-    end
+```ruby
+Honeybadger.configure do |config|
+  config.api_key = '[your-api-key]'
+end
+```
 
 That's it!
 
 ### Rails 2.x
 
-Add the honeybadger gem to your app. In config/environment.rb:
+Add the honeybadger gem to your app. In `config/environment.rb`:
 
-    config.gem 'honeybadger'
+```ruby
+config.gem 'honeybadger'
+```
 
 or if you are using bundler:
 
-    gem 'honeybadger', :require => 'honeybadger/rails'
+```ruby
+gem 'honeybadger', :require => 'honeybadger/rails'
+```
 
-Then from your project's RAILS_ROOT, and in your development environment, run:
+Then from your project's `RAILS_ROOT`, and in your development environment, run:
 
     rake gems:install
     rake gems:unpack GEM=honeybadger
@@ -46,13 +54,15 @@ Then from your project's RAILS_ROOT, and in your development environment, run:
 As always, if you choose not to vendor the honeybadger gem, make sure
 every server you deploy to has the gem installed or your application won't start.
 
-Finally, create an initializer in config/initializers and configure your
+Finally, create an initializer in `config/initializers` and configure your
 API key for your project:
 
-    require 'honeybadger/rails'
-    Honeybadger.configure do |config|
-      config.api_key = '[your-api-key]'
-    end
+```ruby
+  require 'honeybadger/rails'
+  Honeybadger.configure do |config|
+    config.api_key = '[your-api-key]'
+  end
+```
 
 ## Rack
 
@@ -60,36 +70,40 @@ In order to use honeybadger in a non-Rails rack app, just load
 honeybadger, configure your API key, and use the Honeybadger::Rack
 middleware:
 
-    require 'rack'
-    require 'honeybadger'
+```ruby
+require 'rack'
+require 'honeybadger'
 
-    Honeybadger.configure do |config|
-      config.api_key = 'my_api_key'
-    end
+Honeybadger.configure do |config|
+  config.api_key = 'my_api_key'
+end
 
-    app = Rack::Builder.app do
-      run lambda { |env| raise "Rack down" }
-    end
+app = Rack::Builder.app do
+  run lambda { |env| raise "Rack down" }
+end
 
-    use Honeybadger::Rack
-    run app
+use Honeybadger::Rack
+run app
+```
 
 ## Sinatra
 
 Using honeybadger in a Sinatra app is just like a Rack app:
 
-    require 'sinatra'
-    require 'honeybadger'
+```ruby
+require 'sinatra'
+require 'honeybadger'
 
-    Honeybadger.configure do |config|
-      config.api_key = 'my api key'
-    end
+Honeybadger.configure do |config|
+  config.api_key = 'my api key'
+end
 
-    use Honeybadger::Rack
+use Honeybadger::Rack
 
-    get '/' do
-      raise "Sinatra has left the building"
-    end
+get '/' do
+  raise "Sinatra has left the building"
+end
+```
 
 ## Additional integrations:
 
@@ -105,12 +119,14 @@ It intercepts the exception middleware calls, sends notifications and continues
 If you want to log arbitrary things which you've rescued yourself from a
 controller, you can do something like this:
 
-    ...
-    rescue => ex
-      notify_honeybadger(ex)
-      flash[:failure] = 'Encryptions could not be rerouted, try again.'
-    end
-    ...
+```ruby
+# ...
+rescue => ex
+  notify_honeybadger(ex)
+  flash[:failure] = 'Encryptions could not be rerouted, try again.'
+end
+# ...
+```
 
 The `#notify_honeybadger` call will send the notice over to Honeybadger for later
 analysis. While in your controllers you use the `notify_honeybadger` method, anywhere
@@ -137,14 +153,16 @@ task. The following environments are ignored by default: *development*,
 setting the `development_environments` option in your Honeybadger
 initializer:
 
-    Honeybadger.configure do |config|
-      ...
-      # To add an additional environment to be ignored:
-      config.development_environments << 'staging'
+```ruby
+Honeybadger.configure do |config|
+  # ...
+  # To add an additional environment to be ignored:
+  config.development_environments << 'staging'
 
-      # To override the default environments completely:
-      config.development_environments = ['test', 'cucumber']
-    end
+  # To override the default environments completely:
+  config.development_environments = ['test', 'cucumber']
+end
+```
 
 If you choose to override the `development_environments` option for
 whatever reason, please make sure your test environments are ignored.
@@ -155,12 +173,14 @@ Honeybadger allows you to send custom data using `Honeybadger.context`.
 Here's an example of sending some user-specific information in a Rails
 `before_filter` call:
 
-    before_filter do
-      Honeybadger.context({
-        :user_id => current_user.id,
-        :user_email => current_user.email
-      }) if current_user
-    end
+```ruby
+before_filter do
+  Honeybadger.context({
+    :user_id => current_user.id,
+    :user_email => current_user.email
+  }) if current_user
+end
+```
 
 Now, whenever an error occurs, Honeybadger will display the affected
 user's id and email address, if available.
@@ -185,7 +205,9 @@ We officially support deploy tracking using Capistrano and Heroku:
 In order to track deployments using Capistrano, simply require
 Honeybadger's Capistrano task in your `config/deploy.rb` file:
 
-    require 'honeybadger/capistrano'
+```ruby
+require 'honeybadger/capistrano'
+```
 
 If you ran the Honeybadger install generator in a project that was
 previously configured with Capistrano, we already added this for you.
@@ -195,8 +217,10 @@ the server you are deploying to, so that it can correctly report
 environment-related information. To override the task that is run, you
 can set the `:honeybadger_deploy_task` in your *config/deploy.rb* file:
 
-    # Loads Rails environment before executing normal deploy task
-    set :honeybadger_deploy_task, 'honeybadger:deploy_with_environment'
+```ruby
+# Loads Rails environment before executing normal deploy task
+set :honeybadger_deploy_task, 'honeybadger:deploy_with_environment'
+```
 
 If you would prefer to notify Honeybadger locally without using rake,
 check out our blog post: [Honeybadger and Capistrano: the metal way](http://honeybadger.io/blog/2012/10/06/honeybadger-and-capistrano/).
@@ -233,11 +257,11 @@ environment information:
 
 You can optionally add:
 
-* REPO=[scm repo url]
-* REVISION=[scm sha]
-* USER=[local user's name]
-* API_KEY=[a different api key]
-* DRY_RUN=true (simulates notification)
+* `REPO=[scm repo url]`
+* `REVISION=[scm sha]`
+* `USER=[local user's name]`
+* `API_KEY=[a different api key]`
+* `DRY_RUN=true (simulates notification)`
 
 ## Notifying Honeybadger asynchronously
 
@@ -251,73 +275,83 @@ handler can be set directly by setting the `async` configuration option,
 or by passing a block to `config.async` (in this case, a Proc instance
 will be created for you):
 
-    Honeybadger.configure do |config|
-      ...
+```ruby
+Honeybadger.configure do |config|
+  # ...
 
-      # Configuring handler directly:
-      config.async do |notice|
-        # Delivers notification immediately
-        notice.deliver # => 'qwer-asdf-zxcv'
-      end
+  # Configuring handler directly:
+  config.async do |notice|
+    # Delivers notification immediately
+    notice.deliver # => 'qwer-asdf-zxcv'
+  end
 
-      # Using your own handler (identical behavior):
-      config.async = Proc.new { |n| n.deliver }
-    end
+  # Using your own handler (identical behavior):
+  config.async = Proc.new { |n| n.deliver }
+end
+```
 
 We've left the implementation mostly up to you, but here are a few
 examples of notifying Honeybadger asynchronously:
 
 ### Using thread
 
-    Honeybadger.configure do |config|
-      config.async do |notice|
-        Thread.new { notice.deliver }
-      end
-    end
+```ruby
+Honeybadger.configure do |config|
+  config.async do |notice|
+    Thread.new { notice.deliver }
+  end
+end
+```
 
 ### Using Resque
 
-    Honeybadger.configure do |config|
-      config.async do |notice|
-        Resque.enqueue(WorkingBadger, notice.to_json)
-      end
-    end
+```ruby
+Honeybadger.configure do |config|
+  config.async do |notice|
+    Resque.enqueue(WorkingBadger, notice.to_json)
+  end
+end
 
-    class WorkingBadger
-      @queue = :cobra_alert
+class WorkingBadger
+  @queue = :cobra_alert
 
-      def self.perform(notice)
-        Honeybadger.sender.send_to_honeybadger(notice)
-      end
-    end
+  def self.perform(notice)
+    Honeybadger.sender.send_to_honeybadger(notice)
+  end
+end
+```
 
 ### Using Sidekiq
 
-    Honeybadger.configure do |config|
-      config.async do |notice|
-        WorkingBadger.perform_async(notice.to_json)
-      end
-    end
+```ruby
+Honeybadger.configure do |config|
+  config.async do |notice|
+    WorkingBadger.perform_async(notice.to_json)
+  end
+end
 
-    class WorkingBadger
-      include Sidekiq::Worker
+class WorkingBadger
+  include Sidekiq::Worker
 
-      def perform(notice)
-        Honeybadger.sender.send_to_honeybadger(notice)
-      end
-    end
+  def perform(notice)
+    Honeybadger.sender.send_to_honeybadger(notice)
+  end
+end
+```
 
 ### Using GirlFriday
 
-    COBRA_QUEUE = GirlFriday::WorkQueue.new(:honeybadger_notices, :size => 7) do |notice|
-      notice.deliver
-    end
+```ruby
+COBRA_QUEUE = GirlFriday::WorkQueue.new(:honeybadger_notices, :size => 7) do |notice|
+  notice.deliver
+end
 
-    Honeybadger.configure do |config|
-      config.async do |notice|
-        COBRA_QUEUE.push(notice)
-      end
-    end
+Honeybadger.configure do |config|
+  config.async do |notice|
+    COBRA_QUEUE.push(notice)
+  end
+end
+```
 
 ## Going beyond exceptions
 
@@ -325,18 +359,20 @@ You can also pass a hash to `Honeybadger.notify` method and store whatever you w
 not just an exception. And you can also use it anywhere, not just in
 controllers:
 
-    begin
-      params = {
-        # params that you pass to a method that can throw an exception
-      }
-      my_unpredicable_method(*params)
-    rescue => e
-      Honeybadger.notify(
-        :error_class   => "Special Error",
-        :error_message => "Special Error: #{e.message}",
-        :parameters    => params
-      )
-    end
+```ruby
+begin
+  params = {
+    # params that you pass to a method that can throw an exception
+  }
+  my_unpredicable_method(*params)
+rescue => e
+  Honeybadger.notify(
+    :error_class   => "Special Error",
+    :error_message => "Special Error: #{e.message}",
+    :parameters    => params
+  )
+end
+```
 
 While in your controllers you use the `notify_honeybadger` method, anywhere else in
 your code, use `Honeybadger.notify`. Honeybadger will get all the information
@@ -348,14 +384,16 @@ about the error itself. As for a hash, these are the keys you should pass:
 
 Honeybadger merges the hash you pass with these default options:
 
-    {
-      :api_key       => Honeybadger.api_key,
-      :error_message => 'Notification',
-      :backtrace     => caller,
-      :parameters    => {},
-      :session       => {},
-      :context       => {}
-    }
+```ruby
+{
+  :api_key       => Honeybadger.api_key,
+  :error_message => 'Notification',
+  :backtrace     => caller,
+  :parameters    => {},
+  :session       => {},
+  :context       => {}
+}
+```
 
 You can override any of those parameters.
 
@@ -365,8 +403,9 @@ One common request we see is to send shell environment variables along with
 manual exception notification.  We recommend sending them along with CGI data
 or Rack environment (:cgi_data or :rack_env keys, respectively.)
 
-See Honeybadger::Notice#initialize in lib/honeybadger/notice.rb for
-more details.
+See `Honeybadger::Notice#initialize` in
+[lib/honeybadger/notice.rb](https://github.com/honeybadger-io/honeybadger-ruby/blob/master/lib/honeybadger/notice.rb)
+for more details.
 
 ## Filtering
 
@@ -379,30 +418,36 @@ notifications (when #notify is called directly).
 
 Honeybadger ignores the following exceptions by default:
 
-    ActiveRecord::RecordNotFound
-    ActionController::RoutingError
-    ActionController::InvalidAuthenticityToken
-    CGI::Session::CookieStore::TamperedWithCookie
-    ActionController::UnknownAction
-    AbstractController::ActionNotFound
-    Mongoid::Errors::DocumentNotFound
+```ruby
+ActiveRecord::RecordNotFound
+ActionController::RoutingError
+ActionController::InvalidAuthenticityToken
+CGI::Session::CookieStore::TamperedWithCookie
+ActionController::UnknownAction
+AbstractController::ActionNotFound
+Mongoid::Errors::DocumentNotFound
+```
 
 To ignore errors in addition to those, specify their names in your Honeybadger
 configuration block. You may use a string, regexp, or class:
 
-    Honeybadger.configure do |config|
-      config.api_key      = '1234567890abcdef'
-      config.ignore       << /IgnoredError$/
-      config.ignore       << "ActiveRecord::IgnoreThisError"
-      config.ignore       << OtherException
-    end
+```ruby
+Honeybadger.configure do |config|
+  config.api_key      = '1234567890abcdef'
+  config.ignore       << /IgnoredError$/
+  config.ignore       << "ActiveRecord::IgnoreThisError"
+  config.ignore       << OtherException
+end
+```
 
 To ignore *only* certain errors (and override the defaults), use the #ignore_only attribute.
 
-    Honeybadger.configure do |config|
-      config.api_key      = '1234567890abcdef'
-      config.ignore_only  = ["ActiveRecord::IgnoreThisError"] # or [] to ignore no exceptions.
-    end
+```ruby
+Honeybadger.configure do |config|
+  config.api_key      = '1234567890abcdef'
+  config.ignore_only  = ["ActiveRecord::IgnoreThisError"] # or [] to ignore no exceptions.
+end
+```
 
 Subclasses of ignored classes will also be ignored, while strings and
 regexps are compared with the error class name only.
@@ -410,37 +455,45 @@ regexps are compared with the error class name only.
 To ignore certain user agents, add in the #ignore_user_agent attribute as a
 string or regexp:
 
-    Honeybadger.configure do |config|
-      config.api_key      = '1234567890abcdef'
-      config.ignore_user_agent  << /Ignored/
-      config.ignore_user_agent << 'IgnoredUserAgent'
-    end
+```ruby
+Honeybadger.configure do |config|
+  config.api_key      = '1234567890abcdef'
+  config.ignore_user_agent  << /Ignored/
+  config.ignore_user_agent << 'IgnoredUserAgent'
+end
+```
 
 To ignore exceptions based on other conditions, use #ignore_by_filter:
 
-    Honeybadger.configure do |config|
-      config.api_key      = '1234567890abcdef'
-      config.ignore_by_filter do |exception_data|
-        true if exception_data[:error_class] == "RuntimeError"
-      end
-    end
+```ruby
+Honeybadger.configure do |config|
+  config.api_key      = '1234567890abcdef'
+  config.ignore_by_filter do |exception_data|
+    true if exception_data[:error_class] == "RuntimeError"
+  end
+end
+```
 
 To replace sensitive information sent to the Honeybadger service with [FILTERED] use #params_filters:
 
-    Honeybadger.configure do |config|
-      config.api_key      = '1234567890abcdef'
-      config.params_filters << "credit_card_number"
-    end
+```ruby
+Honeybadger.configure do |config|
+  config.api_key      = '1234567890abcdef'
+  config.params_filters << "credit_card_number"
+end
+```
 
 Note that, when rescuing exceptions within an ActionController method,
 honeybadger will reuse filters specified by #filter_parameter_logging.
 
 To disable sending session data:
 
-    Honeybadger.configure do |config|
-      config.api_key      = '1234567890abcdef'
-      config.send_request_session = false
-    end
+```ruby
+Honeybadger.configure do |config|
+  config.api_key      = '1234567890abcdef'
+  config.send_request_session = false
+end
+```
 
 ## Testing
 
@@ -449,11 +502,13 @@ notices generated using #notify when you don't expect it to. You can
 use code like this in your test_helper.rb or spec_helper.rb files to redefine
 that method so those errors are not reported while running tests.
 
-    module Honeybadger
-      def self.notify(exception, opts = {})
-        # do nothing.
-      end
-    end
+```ruby
+module Honeybadger
+  def self.notify(exception, opts = {})
+    # do nothing.
+  end
+end
+```
 
 ## Proxy Support
 
@@ -461,12 +516,14 @@ The notifier supports using a proxy, if your server is not able to
 directly reach the Honeybadger servers. To configure the proxy settings,
 added the following information to your Honeybadger configuration block.
 
-    Honeybadger.configure do |config|
-      config.proxy_host = proxy.host.com
-      config.proxy_port = 4038
-      config.proxy_user = foo # optional
-      config.proxy_pass = bar # optional
-    end
+```ruby
+Honeybadger.configure do |config|
+  config.proxy_host = 'proxy.host.com'
+  config.proxy_port = 4038
+  config.proxy_user = 'foo' # optional
+  config.proxy_pass = 'bar' # optional
+end
+```
 
 ## Troubleshooting
 
@@ -475,10 +532,12 @@ By default, Honeybadger is quiet when your log level is set to INFO
 logs when Honeybadger completes a successful notification, set the
 `config.debug` option to true:
 
-    Honeybadger.configure do |config|
-      ...
-      config.debug = true
-    end
+```ruby
+Honeybadger.configure do |config|
+  # ...
+  config.debug = true
+end
+```
 
 ## Supported Ruby versions
 

data/gemfiles/rack.gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: /Users/josh/code/honeybadger-ruby
   specs:
-    honeybadger (1.6.0)
+    honeybadger (1.6.2)
       json
 
 GEM

data/gemfiles/rails2.3.gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: /Users/josh/code/honeybadger-ruby
   specs:
-    honeybadger (1.6.0)
+    honeybadger (1.6.2)
       json
 
 GEM

data/gemfiles/rails3.0.gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: /Users/josh/code/honeybadger-ruby
   specs:
-    honeybadger (1.6.0)
+    honeybadger (1.6.2)
       json
 
 GEM

data/gemfiles/rails3.1.gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: /Users/josh/code/honeybadger-ruby
   specs:
-    honeybadger (1.6.0)
+    honeybadger (1.6.2)
       json
 
 GEM

data/gemfiles/rails3.2.gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: /Users/josh/code/honeybadger-ruby
   specs:
-    honeybadger (1.6.0)
+    honeybadger (1.6.2)
       json
 
 GEM

data/gemfiles/rails4.gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: /Users/josh/code/honeybadger-ruby
   specs:
-    honeybadger (1.6.0)
+    honeybadger (1.6.2)
       json
 
 GEM

data/gemfiles/rake.gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: /Users/josh/code/honeybadger-ruby
   specs:
-    honeybadger (1.6.0)
+    honeybadger (1.6.2)
       json
 
 GEM

data/gemfiles/sinatra.gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: /Users/josh/code/honeybadger-ruby
   specs:
-    honeybadger (1.6.0)
+    honeybadger (1.6.2)
       json
 
 GEM

data/honeybadger.gemspec

@@ -4,8 +4,8 @@ Gem::Specification.new do |s|
   s.rubygems_version = '1.3.5'
 
   s.name              = 'honeybadger'
-  s.version           = '1.6.1'
-  s.date              = '2013-03-14'
+  s.version           = '1.6.2'
+  s.date              = '2013-04-10'
 
   s.summary     = 'Error reports you can be happy about.'
   s.description = 'Make managing application errors a more pleasant experience.'

data/lib/honeybadger.rb

@@ -12,7 +12,7 @@ require 'honeybadger/sender'
 require 'honeybadger/railtie' if defined?(Rails::Railtie)
 
 module Honeybadger
-  VERSION = '1.6.1'
+  VERSION = '1.6.2'
   LOG_PREFIX = "** [Honeybadger] "
 
   HEADERS = {

data/lib/honeybadger/notice.rb

@@ -347,6 +347,8 @@ module Honeybadger
 
     def rack_env(method)
       rack_request.send(method) if rack_request
+    rescue => e
+      { :error => "Failed to call #{method} on Rack::Request -- #{e.message}" }
     end
 
     def rack_request

data/test/unit/notice_test.rb

@@ -455,6 +455,15 @@ class NoticeTest < Test::Unit::TestCase
     assert_equal session_data, notice.session_data
   end
 
+  unless Gem::Version.new(Rack.release) < Gem::Version.new('1.2')
+    should "fail gracefully when Rack params cannot be parsed" do
+      rack_env = Rack::MockRequest.env_for('http://www.example.com/explode', :method => 'POST', :input => 'foo=bar&bar=baz%')
+      notice = Honeybadger::Notice.new(:rack_env => rack_env)
+      assert_equal 1, notice.params.size
+      assert_match /Failed to call params on Rack::Request/, notice.params[:error]
+    end
+  end
+
   should "not send session data when send_request_session is false" do
     notice = build_notice(:send_request_session => false, :session_data => { :foo => :bar })
     assert_equal nil, notice.session_data

metadata

@@ -1,36 +1,32 @@
 --- !ruby/object:Gem::Specification
 name: honeybadger
 version: !ruby/object:Gem::Version
-  version: 1.6.1
-  prerelease: 
+  version: 1.6.2
 platform: ruby
 authors:
 - Joshua Wood
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-03-14 00:00:00.000000000 Z
+date: 2013-04-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: json
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: cucumber
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
@@ -38,7 +34,6 @@ dependencies:
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
@@ -46,7 +41,6 @@ dependencies:
 - !ruby/object:Gem::Dependency
   name: rspec
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
@@ -54,7 +48,6 @@ dependencies:
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
@@ -62,7 +55,6 @@ dependencies:
 - !ruby/object:Gem::Dependency
   name: fakeweb
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
@@ -70,7 +62,6 @@ dependencies:
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
@@ -78,7 +69,6 @@ dependencies:
 - !ruby/object:Gem::Dependency
   name: sham_rack
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
@@ -86,7 +76,6 @@ dependencies:
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
@@ -94,23 +83,20 @@ dependencies:
 - !ruby/object:Gem::Dependency
   name: bourne
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '1.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '1.0'
 - !ruby/object:Gem::Dependency
   name: shoulda
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
@@ -118,7 +104,6 @@ dependencies:
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
@@ -126,81 +111,71 @@ dependencies:
 - !ruby/object:Gem::Dependency
   name: capistrano
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: rake
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: sinatra
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: aruba
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: appraisal
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
 description: Make managing application errors a more pleasant experience.
@@ -292,6 +267,7 @@ files:
 - test/unit/sender_test.rb
 homepage: http://www.honeybadger.io
 licenses: []
+metadata: {}
 post_install_message: 
 rdoc_options:
 - --charset=UTF-8
@@ -299,23 +275,18 @@ rdoc_options:
 require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
-  none: false
   requirements:
-  - - ! '>='
+  - - '>='
     - !ruby/object:Gem::Version
       version: '0'
-      segments:
-      - 0
-      hash: 3567896080089189096
 required_rubygems_version: !ruby/object:Gem::Requirement
-  none: false
   requirements:
-  - - ! '>='
+  - - '>='
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.23
+rubygems_version: 2.0.3
 signing_key: 
 specification_version: 2
 summary: Error reports you can be happy about.