Trying to reopen Honeybadger module to add local variable context works in development but not production about honeybadger-ruby HOT 3 CLOSED

What error is it throwing? Got a backtrace?

from honeybadger-ruby.

It wasn't throwing any error at all, it simply wasn't working - the honeybadger-local-context code wasn't being called at all.

Bigup @levity for helping me implement the hook using

    alias_method_chain :notify, :context

which is now working like a charm.

Now we get great context when exceptions are thrown in rake tasks and its making debugging the exceptions much easier.

This does make the gem Rails dependent, so if there's a way to have this work without relying on alias_method_chain, that'd be great.

Here's the complete method using alias_method_chain:

require 'honeybadger'
require 'binding_of_caller'

module Honeybadger
  class << self
    def notify_with_context(exception, options = {})

      ctx = binding.of_caller(1)
      vars = eval('local_variables', ctx)
      locals_array = vars.map { |arg| [arg, eval(arg.to_s, ctx)]}

      options[:context] ||= {}
      options[:context][:local_variables] = Hash[*locals_array.flatten(1)]

      puts "Notify called with options: #{options}"

      return notify_without_context(exception, options)
    end
    alias_method_chain :notify, :context
  end
end

@joshuap - Do you see how this could be rewritten to not rely on alias_method_chain?

from honeybadger-ruby.

It should be:

alias_method :notify_without_context, :notify
alias_method :notify, :notify_with_context

from honeybadger-ruby.