honeybadger 1.16.7 → 2.0.0.beta.1

data/Guardfile

@@ -1,5 +0,0 @@
-guard :rspec, :cli => '--format Fuubar --fail-fast', :all_after_pass => false do
-  watch(%r{^spec/.+_spec\.rb$})
-  watch(%r{^lib/(.+)\.rb$})     { |m| "spec/#{m[1]}_spec.rb" }
-  watch('spec/spec_helper.rb')  { "spec" }
-end

data/MIT-LICENSE

@@ -1,32 +0,0 @@
-Copyright (c) 2012-2013, Honeybadger Industries LLC
-Portions Copyright (c) 2012 Noah Lorang
-Portions Copyright (c) 2007-2012, Exceptional DBA Airbrake.io
-Portions Copyright (c) 2009 Brenton Fletcher (http://i.bloople.net i@bloople.net)
-Portions Copyright (c) 2014 Charlie Somerville
-
-The original version of the Honeybadger gem was based on the
-MIT-licensed Airbrake gem. All code contained herein that is 
-copyright Exceptional DBA Airbrake.io was available under the 
-MIT license (listed below) on or before November 6, 2012. 
-
-Permission is hereby granted, free of charge, to any person
-obtaining a copy of this software and associated documentation
-files (the "Software"), to deal in the Software without
-restriction, including without limitation the rights to use,
-copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the
-Software is furnished to do so, subject to the following
-conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
-OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
-HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
-WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
-FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
-OTHER DEALINGS IN THE SOFTWARE.
-

data/Rakefile

@@ -1,159 +0,0 @@
-require 'rubygems'
-require 'bundler/setup'
-require 'appraisal'
-require 'date'
-require 'json'
-
-begin
-  require 'cucumber/rake/task'
-rescue LoadError
-  $stderr.puts "Please install cucumber: `gem install cucumber`"
-  exit 1
-end
-
-#############################################################################
-#
-# Helper methods
-#
-#############################################################################
-
-def name
-  @name ||= Dir['*.gemspec'].first.split('.').first
-end
-
-def version
-  line = File.read("lib/#{name}.rb")[/^\s*VERSION\s*=\s*.*/]
-  line.match(/.*VERSION\s*=\s*['"](.*)['"]/)[1]
-end
-
-def date
-  Date.today.to_s
-end
-
-def rubyforge_project
-  name
-end
-
-def gemspec_file
-  "#{name}.gemspec"
-end
-
-def gem_file
-  "#{name}-#{version}.gem"
-end
-
-def replace_header(head, header_name)
-  head.sub!(/(\.#{header_name}\s*= ').*'/) { "#{$1}#{send(header_name)}'"}
-end
-
-#############################################################################
-#
-# Standard tasks
-#
-#############################################################################
-
-require 'rspec/core/rake_task'
-RSpec::Core::RakeTask.new(:spec)
-task :default => :spec
-task :test => :spec
-
-Cucumber::Rake::Task.new(:cucumber) do |t|
-  t.fork = true
-  t.cucumber_opts = ['--format', 'progress', '--tags', '~@pending']
-
-  unless ENV['BUNDLE_GEMFILE'] =~ /rails[^2]/
-    t.cucumber_opts << '--tags ~@rails_3'
-  end
-
-  if ENV['BUNDLE_GEMFILE'] =~ /rails3/
-    t.cucumber_opts << 'features/rails3.x.feature'
-  end
-
-  case ENV['BUNDLE_GEMFILE']
-  when /rails/
-    t.cucumber_opts << 'features/rails.feature features/metal.feature'
-  when /rack/
-    t.cucumber_opts << 'features/rack.feature'
-  when /rake/
-    t.cucumber_opts << 'features/rake.feature'
-  when /thor/
-    t.cucumber_opts << 'features/thor.feature'
-  when /sinatra/
-    t.cucumber_opts << 'features/sinatra.feature'
-  else
-    t.cucumber_opts << 'features/standalone.feature'
-  end unless ENV['FEATURE']
-end
-
-desc "Open an irb session preloaded with this library"
-task :console do
-  sh "irb -rubygems -r ./lib/#{name}.rb"
-end
-
-#############################################################################
-#
-# Packaging tasks
-#
-#############################################################################
-
-desc "Create tag v#{version} and build and push #{gem_file} to Rubygems"
-task :release => :build do
-  unless `git branch` =~ /^\* master$/
-    puts "You must be on the master branch to release!"
-    exit!
-  end
-  sh "git commit --allow-empty -a -e -m 'Release #{version}'"
-  sh "git tag v#{version}"
-  sh "git push origin master"
-  sh "git push origin v#{version}"
-  sh "gem push pkg/#{name}-#{version}.gem"
-end
-
-desc "Build #{gem_file} into the pkg directory"
-task :build => :gemspec do
-  sh "mkdir -p pkg"
-  sh "gem build #{gemspec_file}"
-  sh "mv #{gem_file} pkg"
-end
-
-desc "Generate #{gemspec_file}"
-task :gemspec => :validate do
-  # read spec file and split out manifest section
-  spec = File.read(gemspec_file)
-  head, manifest, tail = spec.split("  # = MANIFEST =\n")
-
-  # replace name version and date
-  replace_header(head, :name)
-  replace_header(head, :version)
-  replace_header(head, :date)
-  #comment this out if your rubyforge_project has a different name
-  replace_header(head, :rubyforge_project)
-
-  # determine file list from git ls-files
-  files = `git ls-files`.
-    split("\n").
-    sort.
-    reject { |file| file =~ /^\./ }.
-    reject { |file| file =~ /^(rdoc|pkg)/ }.
-    map { |file| "    #{file}" }.
-    join("\n")
-
-  # piece file back together and write
-  manifest = "  s.files = %w[\n#{files}\n  ]\n"
-  spec = [head, manifest, tail].join("  # = MANIFEST =\n")
-  File.open(gemspec_file, 'w') { |io| io.write(spec) }
-  puts "Updated #{gemspec_file}"
-end
-
-desc "Validate #{gemspec_file}"
-task :validate do
-  libfiles = Dir['lib/*'] - ["lib/#{name}.rb", "lib/#{name}_tasks.rb", "lib/#{name}", "lib/rails"]
-  unless libfiles.empty?
-    puts "Directory `lib` should only contain `#{name}.rb` and `#{name}_tasks.rb` files, and `#{name}` and lib/rails dir."
-    exit!
-  end
-  unless Dir['VERSION*'].empty?
-    puts "A `VERSION` file at root level violates Gem best practices."
-    exit!
-  end
-end

data/features/metal.feature

@@ -1,20 +0,0 @@
-Feature: Rescue errors in Rails middleware
-
-  Background:
-    Given I generate a new Rails application
-    And I configure the Honeybadger shim
-    And I configure Honeybadger with:
-      """
-      config.api_key = 'myapikey'
-      config.logger = Logger.new(STDOUT)
-      """
-
-  Scenario: Rescue an exception in the dispatcher
-    When I define a Metal endpoint called "Exploder":
-      """
-      def self.call(env)
-        raise "Explode"
-      end
-      """
-    When I perform a request to "http://example.com:123/metal/index?param=value"
-    Then I should receive a Honeybadger notification

data/features/rack.feature

@@ -1,55 +0,0 @@
-Feature: Use the notifier in a plain Rack app
-
-  Scenario: Rescue and exception in a Rack app
-    Given the following Rack app:
-      """
-      require 'rack'
-      require 'honeybadger'
-
-      Honeybadger.configure do |config|
-        config.api_key = 'my_api_key'
-        config.logger = Logger.new STDOUT
-      end
-
-      app = Rack::Builder.app do
-        use Honeybadger::Rack
-        run lambda { |env| raise "Rack down" }
-      end
-      """
-    When I perform a Rack request to "http://example.com:123/test/index?param=value"
-    Then I should receive a Honeybadger notification
-
-  Scenario: Ignore user agents
-    Given the following Rack app:
-      """
-      require 'rack'
-      require 'honeybadger'
-
-      Honeybadger.configure do |config|
-        config.api_key = 'my_api_key'
-        config.ignore_user_agent << /ignore/
-        config.logger = Logger.new STDOUT
-      end
-
-      class Mock
-        class AppendUserAgent
-          def initialize(app)
-            @app = app
-          end
-
-          def call(env)
-            env["HTTP_USER_AGENT"] = "ignore"
-            @app.call(env)
-          end
-        end
-      end
-
-      app = Rack::Builder.app do
-        use Honeybadger::Rack
-        use Mock::AppendUserAgent
-        run lambda { |env| raise "Rack down" }
-      end
-      """
-    When I perform a Rack request to "http://example.com:123/test/index?param=value"
-    Then the output should not contain "** [Honeybadger] Response from Honeybadger:"
-

data/features/rails.feature

@@ -1,343 +0,0 @@
-Feature: Install the Gem in a Rails application
-
-  Background:
-    Given I generate a new Rails application
-    And I configure the Honeybadger shim
-
-  Scenario: Use the gem without vendoring the gem in a Rails application
-    When I run the honeybadger generator with "-k myapikey"
-    Then I should receive a Honeybadger notification
-    And I should see the Rails version
-
-  Scenario: Configure the notifier by hand
-    When I configure my application to require Honeybadger
-    And I configure the notifier to use "myapikey" as an API key
-    And I run the honeybadger generator with ""
-    Then I should receive a Honeybadger notification
-
-  Scenario: Configuration within initializer isn't overridden by Railtie
-    When I configure my application to require Honeybadger
-    And I run the honeybadger generator with "-k myapikey"
-    And I configure Honeybadger with:
-      """
-      config.api_key = "myapikey"
-      config.project_root = "argle/bargle"
-      """
-    And I run `rake honeybadger:test`
-    Then the output should contain "argle/bargle"
-
-  Scenario: Try to install without an api key
-    When I configure my application to require Honeybadger
-    And I run the honeybadger generator with ""
-    Then the output should contain "Must pass --api-key or --heroku or create config/initializers/honeybadger.rb"
-
-  Scenario: Configure and deploy with Capistrano
-    When I install capistrano
-    And I configure my application to require Honeybadger
-    And I run the honeybadger generator with "-k myapikey"
-    And I run `cap -T`
-    Then the output should contain "honeybadger:deploy"
-
-  Scenario: Try to install when the honeybadger plugin still exists
-    When I install the "honeybadger" plugin
-    And I configure the notifier to use "myapikey" as an API key
-    And I configure my application to require Honeybadger
-    And I run the honeybadger generator with ""
-    Then the output should contain "You must first remove the honeybadger plugin. Please run: script/plugin remove honeybadger"
-
-  @rails_3
-  Scenario: Running the test task with config.force_ssl enabled
-    When I configure Rails with:
-      """
-      config.force_ssl = true
-      """
-    And I configure the notifier to use "myapikey" as an API key
-    And I configure my application to require Honeybadger
-    And I run `rake honeybadger:test`
-    Then I should receive a Honeybadger notification
-
-  @rails_3
-  Scenario: Running the test task with better_errors installed
-    When I configure Rails with:
-      """
-      require 'better_errors'
-      """
-    And I configure the notifier to use "myapikey" as an API key
-    And I configure my application to require Honeybadger
-    And I run `rake honeybadger:test`
-    Then the output should contain "Better Errors detected"
-    And I should receive a Honeybadger notification
-
-  @rails_3
-  Scenario: Running the test task with rack-mini-profiler installed
-    When I configure Rails with:
-      """
-      require 'rack-mini-profiler'
-      """
-    And I configure the notifier to use "myapikey" as an API key
-    And I configure my application to require Honeybadger
-    And I run `rake honeybadger:test`
-    Then the output should not contain "rake aborted"
-    And I should receive a Honeybadger notification
-
-  Scenario: Rescue an exception in a controller
-    When I configure my application to require Honeybadger
-    And I configure Honeybadger with:
-      """
-      config.api_key = 'myapikey'
-      config.logger = Logger.new(STDOUT)
-      """
-    And I define a response for "TestController#index":
-      """
-      session[:value] = "test"
-      raise RuntimeError, "some message"
-      """
-    And I route "/test/index" to "test#index"
-    And I perform a request to "http://example.com:123/test/index?param=value"
-    Then I should receive a Honeybadger notification
-
-  Scenario: Rescue an exception in a metal controller
-    When I configure my application to require Honeybadger
-    And I configure Honeybadger with:
-      """
-      config.api_key = 'myapikey'
-      config.logger = Logger.new(STDOUT)
-      """
-    And I define a metal response for "TestController#index":
-      """
-      raise RuntimeError, "some message"
-      """
-    And I route "/test/index" to "test#index"
-    And I perform a request to "http://example.com:123/test/index?param=value"
-    Then I should receive a Honeybadger notification
-
-  Scenario: Output when user informer is enabled
-    When I configure my application to require Honeybadger
-    And I configure Honeybadger with:
-      """
-      config.api_key = 'myapikey'
-      config.logger = Logger.new(STDOUT)
-      """
-    And I define a response for "TestController#index":
-      """
-      session[:value] = "test"
-      raise RuntimeError, "some message"
-      """
-    And I configure the user informer
-    And I route "/test/index" to "test#index"
-    And I perform a request to "http://example.com:123/test/index?param=value"
-    Then the output should contain "Honeybadger Error 123456789"
-    And the output should not contain "<!-- HONEYBADGER ERROR -->"
-
-  Scenario: Output when user feedback is enabled
-    When I configure my application to require Honeybadger
-    And I configure Honeybadger with:
-      """
-      config.api_key = 'myapikey'
-      config.logger = Logger.new(STDOUT)
-      """
-    And I define a response for "TestController#index":
-      """
-      session[:value] = "test"
-      raise RuntimeError, "some message"
-      """
-    And I configure the user feedback form
-    And I route "/test/index" to "test#index"
-    And I perform a request to "http://example.com:123/test/index?param=value"
-    Then the output should contain "honeybadger_feedback_token"
-    And the output should not contain "<!-- HONEYBADGER FEEDBACK -->"
-
-  Scenario: Log output in production environments
-    When I configure my application to require Honeybadger
-    And I configure Honeybadger with:
-      """
-      config.api_key = 'myapikey'
-      config.logger = Logger.new(STDOUT)
-      config.logger.level = Logger::INFO
-      """
-    And I define a response for "TestController#index":
-      """
-      raise RuntimeError, "some message"
-      """
-    And I route "/test/index" to "test#index"
-    And I perform a request to "http://example.com:123/test/index?param=value"
-    Then the output should match /\[Honeybadger\] Notifier (?:\S+) ready to catch errors/
-    Then the output should not contain "[Honeybadger] Success"
-    Then the output should not contain "[Honeybadger] Environment Info"
-    Then the output should not contain "[Honeybadger] Response from Honeybadger"
-    Then the output should not contain "[Honeybadger] Notice"
-
-  Scenario: Failure to notify Honeybadger in production environments
-    When I configure the Honeybadger failure shim
-    And I configure my application to require Honeybadger
-    And I configure Honeybadger with:
-      """
-      config.api_key = 'myapikey'
-      config.logger = Logger.new(STDOUT)
-      config.logger.level = Logger::INFO
-      """
-    And I define a response for "TestController#index":
-      """
-      raise RuntimeError, "some message"
-      """
-    And I route "/test/index" to "test#index"
-    And I perform a request to "http://example.com:123/test/index?param=value"
-    Then the output should contain "[Honeybadger] Failure"
-    Then the output should not contain "Honeybadger::Sender#send_to_honeybadger"
-
-  Scenario: The app uses Vlad instead of Capistrano
-    When I configure my application to require Honeybadger
-    And I run `touch config/deploy.rb`
-    And I run `rm Capfile`
-    And I run the honeybadger generator with "-k myapikey"
-    Then the file "config/deploy.rb" should not contain "capistrano"
-
-  Scenario: Support the Heroku addon in the generator
-    When I configure the Heroku gem shim with "myapikey"
-    And I configure my application to require Honeybadger
-    And I run the honeybadger generator with "--heroku"
-    Then I should receive a Honeybadger notification
-    And I should see the Rails version
-    And my Honeybadger configuration should contain the following line:
-      """
-      config.api_key = ENV['HONEYBADGER_API_KEY']
-      """
-
-  Scenario: Support the --app option for the Heroku addon in the generator
-    When I configure the Heroku gem shim with "myapikey" and multiple app support
-    And I configure my application to require Honeybadger
-    And I run the honeybadger generator with "--heroku -a myapp"
-    Then I should receive a Honeybadger notification
-    And I should see the Rails version
-    And my Honeybadger configuration should contain the following line:
-      """
-      config.api_key = ENV['HONEYBADGER_API_KEY']
-      """
-
-  Scenario: Filtering parameters in a controller
-    When I configure my application to require Honeybadger
-    And I configure Honeybadger with:
-      """
-      config.api_key = "myapikey"
-      config.logger = Logger.new(STDOUT)
-      config.params_filters << "credit_card_number"
-      config.params_filters << "secret"
-      config.debug = true
-      """
-    And I define a response for "TestController#index":
-      """
-      params[:credit_card_number] = "red23"
-      raise RuntimeError, "some message"
-      """
-    And I route "/test/index" to "test#index"
-    And I perform a request to "http://example.com:123/test/index?param=value&secret=blue42"
-    Then I should receive a Honeybadger notification
-    And the request should not contain "red23"
-    And the request should not contain "blue42"
-    And the request params should contain "FILTERED"
-
-  Scenario: Filtering session in a controller
-    When I configure my application to require Honeybadger
-    And I configure Honeybadger with:
-      """
-      config.api_key = "myapikey"
-      config.logger = Logger.new(STDOUT)
-      config.params_filters << "secret"
-      config.debug = true
-      """
-    And I define a response for "TestController#index":
-      """
-      session["secret"] = "blue42"
-      raise RuntimeError, "some message"
-      """
-    And I route "/test/index" to "test#index"
-    And I perform a request to "http://example.com:123/test/index?param=value"
-    Then I should receive a Honeybadger notification
-    And the request should not contain "blue42"
-    And the request session should contain "FILTERED"
-
-  Scenario: Filtering session and params based on Rails parameter filters
-    When I configure my application to require Honeybadger
-    And I configure Honeybadger with:
-      """
-      config.api_key = 'myapikey'
-      config.logger = Logger.new(STDOUT)
-      config.debug = true
-      """
-    And I configure the application to filter parameter "secret"
-    And I define a response for "TestController#index":
-      """
-      params["secret"] = "red23"
-      session["secret"] = "blue42"
-      raise RuntimeError, "some message"
-      """
-    And I route "/test/index" to "test#index"
-    And I perform a request to "http://example.com:123/test/index?param=value"
-    Then I should receive a Honeybadger notification
-    And the request should not contain "red23"
-    And the request should not contain "blue42"
-    And the request session should contain "FILTERED"
-    And the request params should contain "FILTERED"
-
-  Scenario: Notify honeybadger within the controller
-    When I configure my application to require Honeybadger
-    And I configure Honeybadger with:
-      """
-      config.api_key = 'myapikey'
-      config.logger = Logger.new(STDOUT)
-      """
-    And I define a response for "TestController#index":
-      """
-      session[:value] = "test"
-      notify_honeybadger(RuntimeError.new("some message"))
-      render :nothing => true
-      """
-    And I route "/test/index" to "test#index"
-    And I perform a request to "http://example.com:123/test/index?param=value"
-    Then I should receive a Honeybadger notification
-
-  Scenario: Reporting 404s
-    When I configure my application to require Honeybadger
-    And I configure Honeybadger with:
-    """
-    config.api_key = 'myapikey'
-    config.logger = Logger.new(STDOUT)
-    config.ignore_only = []
-    """
-    And I perform a request to "http://example.com:123/this/route/does/not/exist"
-    Then the output should contain "The page you were looking for doesn't exist."
-    And I should receive a Honeybadger notification
-
-  Scenario: Asynchronous delivery
-    When I configure my application to require Honeybadger
-    And I configure Honeybadger with:
-      """
-      config.api_key = 'myapikey'
-      config.logger = Logger.new(STDOUT)
-      config.async do |notice|
-        handler = Thread.new do
-          notice.deliver
-        end
-        handler.join
-      end
-      """
-    And I define a response for "TestController#index":
-      """
-      raise RuntimeError, "some message"
-      """
-    And I route "/test/index" to "test#index"
-    And I perform a request to "http://example.com:123/test/index?param=value"
-    Then I should receive a Honeybadger notification
-
-  Scenario: Asynchronous delivery in generator
-    When I configure my application to require Honeybadger
-    And I configure Honeybadger with:
-      """
-      config.api_key = 'myapikey'
-      config.async do |notice|
-        Thread.new { notice.deliver }
-      end
-      """
-    And I run the honeybadger generator with ""
-    Then the output should contain "Temporarily disabling asynchronous delivery"
-    And I should receive a Honeybadger notification