bugsnag 6.13.1 → 6.18.0

data/features/rails_features/handled.feature

@@ -1,42 +0,0 @@
-Feature: Rails handled errors
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Unhandled RuntimeError
-  Given I start the rails service
-  When I navigate to the route "/handled/unthrown" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the event "unhandled" is false
-  And the exception "errorClass" equals "RuntimeError"
-  And the exception "message" starts with "handled unthrown error"
-  And the event "app.type" equals "rails"
-  And the event "metaData.request.url" ends with "/handled/unthrown"
-  And the event "severity" equals "warning"
-  And the event "severityReason.type" equals "handledException"
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Thrown handled NameError
-  Given I start the rails service
-  When I navigate to the route "/handled/thrown" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the exception "errorClass" equals "NameError"
-  And the exception "message" starts with "undefined local variable or method `generate_unhandled_error' for #<HandledController"
-  And the event "unhandled" is false
-  And the event "metaData.request.url" ends with "/handled/thrown"
-  And the event "app.type" equals "rails"
-  And the event "severity" equals "warning"
-  And the event "severityReason.type" equals "handledException"
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Manual string notify
-  Given I start the rails service
-  When I navigate to the route "/handled/string_notify" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the exception "errorClass" equals "RuntimeError"
-  And the exception "message" starts with "handled string"
-  And the event "unhandled" is false
-  And the event "metaData.request.url" ends with "/handled/string_notify"
-  And the event "app.type" equals "rails"
-

data/features/rails_features/ignore_classes.feature

@@ -1,14 +0,0 @@
-Feature: Ignore classes
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Ignore_classes can be set to a different value in initializer
-  Given I set environment variable "BUGSNAG_IGNORE_CLASS" to "IgnoredError"
-  And I start the rails service
-  When I navigate to the route "/ignore_classes/initializer" on the rails app
-  Then I should receive no requests
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Ignore_classes can be set to a different value after initializer
-  Given I start the rails service
-  When I navigate to the route "/ignore_classes/after?ignore=IgnoredError" on the rails app
-  Then I should receive no requests

data/features/rails_features/meta_data_filters.feature

@@ -1,14 +0,0 @@
-Feature: Metadata filters
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Meta_data_filters should include Rails.configuration.filter_parameters
-  Given I start the rails service
-  When I navigate to the route "/metadata_filters/filter" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the event "unhandled" is false
-  And the exception "errorClass" equals "RuntimeError"
-  And the exception "message" starts with "handled string"
-  And the event "app.type" equals "rails"
-  And the event "metaData.request.url" ends with "/metadata_filters/filter"
-  And the event "metaData.my_specific_filter" equals "[FILTERED]"

data/features/rails_features/mongo_breadcrumbs.feature

@@ -1,26 +0,0 @@
-Feature: Mongo automatic breadcrumbs
-
-@rails4 @rails5 @rails6
-Scenario: Successful breadcrumbs
-  Given I start the rails service
-  When I navigate to the route "/mongo/success_crash" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the event contains a breadcrumb matching the JSON fixture in "features/fixtures/expected_breadcrumbs/mongo_success.json"
-
-@rails4 @rails5 @rails6
-Scenario: Breadcrumb with filter parameters
-  Given I start the rails service
-  When I navigate to the route "/mongo/get_crash" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the event contains a breadcrumb matching the JSON fixture in "features/fixtures/expected_breadcrumbs/mongo_filtered_request.json"
-  And the event contains a breadcrumb matching the JSON fixture in "features/fixtures/expected_breadcrumbs/mongo_filtered_result.json"
-
-@rails4 @rails5 @rails6
-Scenario: Failure breadcrumbs
-  Given I start the rails service
-  When I navigate to the route "/mongo/failure_crash" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the event contains a breadcrumb matching the JSON fixture in "features/fixtures/expected_breadcrumbs/mongo_failed.json"

data/features/rails_features/project_root.feature

@@ -1,35 +0,0 @@
-Feature: Project root configuration
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Project_root should default to Rails.root
-  Given I start the rails service
-  When I navigate to the route "/project_root/default" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the exception "errorClass" equals "RuntimeError"
-  And the exception "message" starts with "handled string"
-  And the event "metaData.request.url" ends with "/project_root/default"
-  And the "file" of the top non-bugsnag stackframe equals "app/controllers/project_root_controller.rb"
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Project_root can be set in an initializer
-  Given I set environment variable "BUGSNAG_PROJECT_ROOT" to "/foo/bar"
-  And I start the rails service
-  When I navigate to the route "/project_root/initializer" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the exception "errorClass" equals "RuntimeError"
-  And the exception "message" starts with "handled string"
-  And the event "metaData.request.url" ends with "/project_root/initializer"
-  And the "file" of the top non-bugsnag stackframe equals "/usr/src/app/controllers/project_root_controller.rb"
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Project_root can be set after an initializer
-  Given I start the rails service
-  When I navigate to the route "/project_root/after" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the exception "errorClass" equals "RuntimeError"
-  And the exception "message" starts with "handled string"
-  And the event "metaData.request.url" ends with "/project_root/after"
-  And the "file" of the top non-bugsnag stackframe equals "/usr/src/app/controllers/project_root_controller.rb"

data/features/rails_features/release_stage.feature

@@ -1,27 +0,0 @@
-Feature: Release stage
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Release_stage should default to RAILS_ENV
-  Given I set environment variable "RAILS_ENV" to "rails_env"
-  And I start the rails service
-  When I navigate to the route "/release_stage/default" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the event "app.releaseStage" equals "rails_env"
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Release_stage can be set in an initializer
-  Given I set environment variable "BUGSNAG_RELEASE_STAGE" to "maze_release_stage_env"
-  And I start the rails service
-  When I navigate to the route "/release_stage/default" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the event "app.releaseStage" equals "maze_release_stage_env"
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Release_stage can be set after an initializer
-  Given I start the rails service
-  When I navigate to the route "/release_stage/after?stage=set_after_env" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the event "app.releaseStage" equals "set_after_env"

data/features/rails_features/send_code.feature

@@ -1,18 +0,0 @@
-Feature: Send code
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Send_code can be updated in an initializer
-  Given I set environment variable "BUGSNAG_SEND_CODE" to "false"
-  And I start the rails service
-  When I navigate to the route "/send_code/initializer" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the event "exceptions.0.stacktrace.0.code" is null
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Send_code can be updated after an initializer
-  Given I start the rails service
-  When I navigate to the route "/send_code/after" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the event "exceptions.0.stacktrace.0.code" is null

data/features/rails_features/send_environment.feature

@@ -1,13 +0,0 @@
-Feature: Send environment
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Send_environment should send environment in handled errors when true
-  Given I set environment variable "BUGSNAG_SEND_ENVIRONMENT" to "true"
-  And I start the rails service
-  When I navigate to the route "/send_environment/initializer" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the exception "errorClass" equals "RuntimeError"
-  And the exception "message" starts with "handled string"
-  And the event "metaData.environment.REQUEST_METHOD" equals "GET"
-  And the event "app.type" equals "rails"

data/features/rails_features/unhandled.feature

@@ -1,16 +0,0 @@
-Feature: Unhandled exceptions support
-
-@rails3 @rails4 @rails5 @rails6
-Scenario: Unhandled RuntimeError
-  Given I start the rails service
-  When I navigate to the route "/unhandled/error" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the event "unhandled" is true
-  And the exception "errorClass" equals "NameError"
-  And the exception "message" starts with "undefined local variable or method `generate_unhandled_error' for #<UnhandledController"
-  And the event "app.type" equals "rails"
-  And the event "metaData.request.url" ends with "/unhandled/error"
-  And the event "severity" equals "error"
-  And the event "severityReason.type" equals "unhandledExceptionMiddleware"
-  And the event "severityReason.attributes.framework" equals "Rack"

data/features/rails_features/user_info.feature

@@ -1,52 +0,0 @@
-Feature: Capture user information
-
-@rails3
-Scenario Outline: Warden user information is sent
-  Given I start the rails service
-  When I navigate to the route "/warden/create" on the rails app
-  And I navigate to the route "/warden/<route>?email=testtest@test.test" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the event "user.email" equals "testtest@test.test"
-  And the event "user.name" equals "Warden User"
-  And the event "user.first_name" equals "Warden"
-  And the event "user.last_name" equals "User"
-
-  Examples:
-    | route     |
-    | handled   |
-    | unhandled |
-
-@rails4
-Scenario Outline: Devise user information is sent
-  Given I start the rails service
-  When I navigate to the route "/devise/create" on the rails app
-  And I navigate to the route "/devise/<route>" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the event "user.email" equals "test+test@test.test"
-  And the event "user.name" equals "Devise User"
-  And the event "user.first_name" equals "Devise"
-  And the event "user.last_name" equals "User"
-
-  Examples:
-    | route     |
-    | handled   |
-    | unhandled |
-
-@rails5 @rails6
-Scenario Outline: Clearance user information is sent
-  Given I start the rails service
-  When I navigate to the route "/clearance/create" on the rails app
-  And I navigate to the route "/clearance/<route>" on the rails app
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the event "user.email" equals "testtest@test.test"
-  And the event "user.name" equals "Clearance User"
-  And the event "user.first_name" equals "Clearance"
-  And the event "user.last_name" equals "User"
-
-  Examples:
-    | route     |
-    | handled   |
-    | unhandled |

data/features/sidekiq.feature

@@ -1,30 +0,0 @@
-Feature: Bugsnag raises errors in Sidekiq workers
-
-Scenario: An unhandled RuntimeError sends a report
-  Given I run the service "sidekiq" with the command "bundle exec rake sidekiq_tests:unhandled_error"
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the event "unhandled" is true
-  And the event "severity" equals "error"
-  And the event "context" equals "UnhandledError@default"
-  And the event "severityReason.type" equals "unhandledExceptionMiddleware"
-  And the event "severityReason.attributes.framework" equals "Sidekiq"
-  And the exception "errorClass" equals "RuntimeError"
-  And the "file" of stack frame 0 equals "/app/app.rb"
-  And the "lineNumber" of stack frame 0 equals 33
-  And the payload field "events.0.metaData.sidekiq" matches the appropriate Sidekiq unhandled payload
-  And the event "metaData.sidekiq.msg.created_at" is a parsable timestamp in seconds
-  And the event "metaData.sidekiq.msg.enqueued_at" is a parsable timestamp in seconds
-
-Scenario: A handled RuntimeError can be notified
-  Given I run the service "sidekiq" with the command "bundle exec rake sidekiq_tests:handled_error"
-  And I wait to receive a request
-  Then the request is valid for the error reporting API version "4.0" for the "Ruby Bugsnag Notifier"
-  And the event "unhandled" is false
-  And the event "context" equals "HandledError@default"
-  And the event "severity" equals "warning"
-  And the event "severityReason.type" equals "handledException"
-  And the exception "errorClass" equals "RuntimeError"
-  And the payload field "events.0.metaData.sidekiq" matches the appropriate Sidekiq handled payload
-  And the event "metaData.sidekiq.msg.created_at" is a parsable timestamp in seconds
-  And the event "metaData.sidekiq.msg.enqueued_at" is a parsable timestamp in seconds

data/features/steps/ruby_notifier_steps.rb

@@ -1,75 +0,0 @@
-Then(/^the "(.+)" of the top non-bugsnag stackframe equals (\d+|".+")$/) do |element, value|
-  stacktrace = read_key_path(Server.current_request[:body], 'events.0.exceptions.0.stacktrace')
-  frame_index = stacktrace.find_index { |frame| ! /.*lib\/bugsnag.*\.rb/.match(frame["file"]) }
-  steps %Q{
-    the "#{element}" of stack frame #{frame_index} equals #{value}
-  }
-end
-
-Then(/^the total sessionStarted count equals (\d+)$/) do |value|
-  session_counts = read_key_path(Server.current_request[:body], "sessionCounts")
-  total_count = session_counts.inject(0) { |count, session| count += session["sessionsStarted"] }
-  assert_equal(value, total_count)
-end
-
-
-# Due to an ongoing discussion on whether the `payload_version` needs to be present within the headers
-# and body of the payload, this step is a local replacement for the similar step present in the main
-# maze-runner library. Once the discussion is resolved this step should be removed and replaced in scenarios
-# with the main library version.
-Then("the request is valid for the error reporting API version {string} for the {string}") do |payload_version, notifier_name|
-  steps %Q{
-    Then the "Bugsnag-Api-Key" header equals "#{$api_key}"
-    And the payload field "apiKey" equals "#{$api_key}"
-    And the "Bugsnag-Payload-Version" header equals "#{payload_version}"
-    And the "Content-Type" header equals "application/json"
-    And the "Bugsnag-Sent-At" header is a timestamp
-
-    And the payload field "notifier.name" equals "#{notifier_name}"
-    And the payload field "notifier.url" is not null
-    And the payload field "notifier.version" is not null
-    And the payload field "events" is a non-empty array
-
-    And each element in payload field "events" has "severity"
-    And each element in payload field "events" has "severityReason.type"
-    And each element in payload field "events" has "unhandled"
-    And each element in payload field "events" has "exceptions"
-  }
-end
-
-Given("I start the rails service") do
-  rails_version = ENV["RAILS_VERSION"]
-  steps %Q{
-    When I start the service "rails#{rails_version}"
-    And I wait for the host "rails#{rails_version}" to open port "3000"
-  }
-end
-
-When("I navigate to the route {string} on the rails app") do |route|
-  rails_version = ENV["RAILS_VERSION"]
-  steps %Q{
-    When I open the URL "http://rails#{rails_version}:3000#{route}"
-  }
-end
-
-Then("the payload field {string} matches the appropriate Sidekiq handled payload") do |field|
-  if ENV["SIDEKIQ_VERSION"] == "~> 2"
-    created_at_present = "false"
-  else
-    created_at_present = "true"
-  end
-  steps %Q{
-    And the payload field "#{field}" matches the JSON fixture in "features/fixtures/sidekiq/payloads/handled_metadata_ca_#{created_at_present}.json"
-  }
-end
-
-Then("the payload field {string} matches the appropriate Sidekiq unhandled payload") do |field|
-  if ENV["SIDEKIQ_VERSION"] == "~> 2"
-    created_at_present = "false"
-  else
-    created_at_present = "true"
-  end
-  steps %Q{
-    And the payload field "#{field}" matches the JSON fixture in "features/fixtures/sidekiq/payloads/unhandled_metadata_ca_#{created_at_present}.json"
-  }
-end

data/features/support/env.rb

@@ -1,23 +0,0 @@
-require 'fileutils'
-
-def install_fixture_gems
-  throw Error.new("Bugsnag.gem not found. Is this running in a docker-container?") unless File.exist?("/app/bugsnag.gem")
-  Dir.entries('features/fixtures').reject { |entry| ['.', '..'].include?(entry) }.each do |entry|
-    target_dir = "features/fixtures/#{entry}"
-    if File.directory?(target_dir)
-      `cp /app/bugsnag.gem #{target_dir}`
-      `gem unpack #{target_dir}/bugsnag.gem --target #{target_dir}/temp-bugsnag-lib`
-    end
-  end
-end
-
-AfterConfiguration do |config|
-  install_fixture_gems
-end
-
-Before do
-  Docker.compose_project_name = "#{rand.to_s}:#{Time.new.strftime("%s")}"
-  Runner.environment.clear
-  Runner.environment["BUGSNAG_API_KEY"] = $api_key
-  Runner.environment["BUGSNAG_ENDPOINT"] = "http://maze-runner:#{MOCK_API_PORT}"
-end

data/issue_template.md

@@ -1,48 +0,0 @@
-### Description
-<!-- A quick description of what you're trying to accomplish -->
-
-### Issue
-<!--
-  What went wrong? (If this issue is a general question or a proposed change,
-  feel free to delete this and subsequent sections.
--->
-
-### Environment
-
-Library versions:
-
-<!--
-  Paste the output of this command into the code block below:
-    bundle list | grep -E "(bugsnag|rails|sidekiq|que|sinatra|resque|shoryuken|mailman|delayed_job)"
--->
-```
-
-```
-
-- OS / OS version:
-- debug mode or production?:
-
-<!--
-  Below are a few approaches you might take to communicate the issue, in
-  descending order of awesomeness. Please choose one and feel free to delete
-  the others from this template.
--->
-### Example Repo
-
-- [ ] Create a minimal repository that can reproduce the issue after running
-  `bundle install` and `rackup` (or `rails server`, or `ruby some-script.rb`,
-  etc)
-- [ ] Link to it here:
-
-### Example code snippet
-
-```ruby
-require 'bugsnag'
-
-# (Insert code sample to reproduce the problem)
-```
-
-<!-- Error messages, if any -->
-```
-
-```