All Versions
56
Latest Version
Avg Release Cycle
46 days
Latest Release
61 days ago

Changelog History
Page 2

  • v4.2.0

    January 31, 2019

    🔄 Changed

    ➕ Added

    • 🚅 Get the right controller / action name in Rails, when using an exception app for custom error pages. -@fernandes
  • v4.1.0

    October 16, 2018

    ➕ Added

    • ➕ Added flag --skip-rails-load to cli commands for optionally skipping Rails initialization when running from a Rails root.

    🛠 Fixed

    • ➕ Added missing Backend::Server#check_in specs
    • 🛠 Fix a memory leak in the worker queue (jruby)
  • v4.0.0

    August 21, 2018

    ➕ Added

    • ➕ Added before_notify hooks to be defined, this allows setting up of multiple hooks which will be invoked with a notice before a notice is sent. Each before_notify hook MUST be a callable (lambda, Proc etc,) with an arity of 1.
    • ➕ Added the ability to halt notices in callbacks using notice.halt!
    • 👉 Make essential attributes on Notice writable: ruby Honeybadger.configure do |config| config.before_notify do |notice| notice.api_key = 'custom api key', notice.error_message = "badgers!", notice.error_class = 'MyError', notice.backtrace = ["/path/to/file.rb:5 in `method'"], notice.fingerprint = 'some unique string', notice.tags = ['foo', 'bar'], notice.context = { user: 33 }, notice.controller = 'MyController', notice.action = 'index', notice.parameters = { q: 'badgers?' }, notice.session = { uid: 42 }, notice.url = "/badgers", end end

    🛠 Fixed

    • 🚦 Ignore SIGTERM SignalExceptions.

    ✂ Removed

    • ✂ Removed Notice#[]

    🔄 Changed

    • 💎 The public method Notice#backtrace is now exposed as the raw Ruby backtrace instead of an instance of Honeybadger::Backtrace (a private class).

    Before:

      notice.backtrace # => #<Honeybadger::Backtrace>
    

    After:

      notice.backtrace # => ["/path/to/file.rb:5 in `method'"]
    
    • 0️⃣ notice[:context] now defaults to an empty Hash instead of nil.

    Before:

      notice[:context] # => nil
    

    After:

      notice[:context] # => {}
    
    • 🖨 The public method Notice#fingerprint now returns the original String which was passed in from the :fingerprint option or the exception_fingerprint callback, not a SHA1 hashed value. The value is still hashed before sending through to the API.
    • 🗄 The public method Honeybadger.exception_filter has been deprecated in favor of before_notify: ruby Honeybadger.configure do |config| config.before_notify do |notice| notice.halt! end end
    • 🗄 The public method Honeybadger.exception_fingerprint has been deprecated in favor of before_notify: ruby Honeybadger.configure do |config| config.before_notify do |notice| notice.fingerprint = 'new fingerprint' end end
    • 🗄 The public method Honeybadger.backtrace_filter has been deprecated in favor of before_notify: ruby Honeybadger.configure do |config| config.before_notify do |notice| notice.backtrace.reject!{|x| x =~ /gem/} end end

    ✂ Removed

    • 🚚 The disabled option is now removed, Use the report_data option instead.
  • v3.3.1

    August 02, 2018

    🛠 Fixed

    • 🛠 Fix synchronous throttling in shoryuken
  • v3.3.0

    January 29, 2018

    🔄 Changed

    • 👉 Use prepend to add Sidekiq Middleware to fix context getting cleared.
    • ➕ Add Rack::QueryParser::ParameterTypeError and Rack::QueryParser::InvalidParameterError to default ignore list.

    🛠 Fixed

    • 🚅 Use a unique route name in rails to avoid name conflicts.
    • 🛠 Fix at_exit callback being skipped in rails apps with a sinatra dependency.
  • v3.2.0

    November 27, 2017

    🔄 Changed

    • Objects which explicitly alias #to_s to #inspect (such as OpenStruct) are now sanitized. '#<OpenStruct attribute="value">' becomes '#<OpenStruct>'. If you pass the value of #inspect (as a String) directly to Honeybadger (or return it from #to_honeybadger), the value will not be sanitized.
    • We're now using String(object) instead of object.to_s as the last resort during sanitization.

    ➕ Added

    • 👻 The exception cause may now be set using an optional :cause option when calling Honeybadger.notify. If not present, the exception's cause will be used, or the global $! exception if available.
    • Any object can now act as context using the #to_honeybadger_context method. The method should have no arguments and return a Hash of context data. Context from exceptions which define this method will automatically be included in error reports.
    • Final object representations in Honeybadger (normally the value of #to_s for unknown types) can be changed by defining the #to_honeybadger method. If the method is defined, the return value of that method will be sent to Honeybadger instead of the #to_s value (for context values, local variables, etc.).
    • '[RAISED]' is returned when object.to_honeybadger or String(object) fails.
    • ➕ Added Honeybadger.check_in method which allows performing check ins from ruby.

    🛠 Fixed

    • 0️⃣ We no longer use "/dev/null" as the default log device as it doesn't exist on Windows.
    • 🔊 Logs when reporting errors in development mode now mention that the error wasn't actually reported. :)
    • 👌 Support new Sidekiq job params key.
    • 🚚 Move at_exit callback to an appropriate place for sinatra apps, so that it does not prematurely stop honeybadger workers.
    • BasicObject, which previously could not be serialized, is now serialized as "#<BasicObject>".
  • v3.1.2

    April 20, 2017

    🛠 Fixed

    • 🛠 Fixed a bug in the Resque plugin which prevented error reports from being sent. The issue was that the Resque's callbacks were executed in an unexpected order which caused the queue to be flushed before error notification instead of after.
  • v3.1.1

    April 13, 2017

    🛠 Fixed

    • 🚀 honeybadger deploy cli command now reads default environment from honeybadger.yml/environment variable.
    • 🛠 Fixed a conflict with the web-console gem.
  • v3.1.0

    March 01, 2017

    🔄 Changed

    • Exceptions encountered while loading/evaluating honeybadger.yml are now raised instead of logged.

    ➕ Added

    • Friendlier backtraces for exceptions originating in honeybadger.yml.
    • 🔔 Notify errors in Shoryuken batches -@phstc

    🛠 Fixed

    • 🚅 Rails environment is now loaded when running honeybadger cli from a Rails root. This fixes an issue where programmatic configuration from Rails was not loaded.
    • 🛠 Fixed logger isn't being overridden properly when configuring with Honeybadger.configure -@anujbiyani
  • v3.0.2

    February 16, 2017

    🛠 Fixed

    • 🛠 Fixed a bug caused by an interaction with the semantic_logger gem.