Swallowed exceptions about honeybadger-ruby HOT 11 CLOSED

Hey Ben, good catch, and thanks for the example app! I'm working on fixing this. In the meantime, does the gem operate normally if you add the secret token back as the exception message suggests?

from honeybadger-ruby.

Yeah, it works fine as long as I fix that.

from honeybadger-ruby.

This is fixed in eb5d593 which will be released in v2.0.

from honeybadger-ruby.

I having the same problem. What can I do to be able to see the backtrace as normally in development env without removing the Honeybadger gem? I'm not able to see the exception message, just the "Something went wrong" screen :(

Thanks

from honeybadger-ruby.

Upgrade to 1.13.2! I released a bugfix for this today. :)

from honeybadger-ruby.

Weird! I have upgraded to 1.13.2 but still doesn't work.

honeybadger (1.13.2)
  json

I have made a little fix on my honeybadger initializer module, explicitly enabling it only when environment is not development, so now I'm able to check the backtrace for now. It looks like this:

if not Rails.env.development?
    Honeybadger.configure do |config|
      config.api_key = 'my_key'
    end
end

Also in Gemfile it is only in production group

group :production do
  gem 'honeybadger'
end

Thanks

from honeybadger-ruby.

Weird, the new gem should handle the session key issue. Can you post a gist with the exception/backtrace from your logs?

from honeybadger-ruby.

Well, it is not exactly the same exception, actually in my case, Honeybadger is swallowing all exception and the app only showing the Rails 500 error page.

This how my terminal looks like with honeybadger enabled:

Started GET "/cases" for 127.0.0.1 at 2014-05-22 16:19:45 -0600
Processing by CasesController#index as HTML
Completed 500 Internal Server Error in 24.2ms

The code generating the exception:

class CasesController < ApplicationController
  layout 'application'

  def index
    Float(nil)
  end
end

The exception message without honeybadger enabled should be:

TypeError in CasesController#index
can't convert nil into Float

And finally an screenshot of the famous error screen:

• Helmy

from honeybadger-ruby.

That's something that Honeybadger would normally catch. Can you email [email protected] with the information outlined here? http://docs.honeybadger.io/article/92-how-to-contact-support-about-gem-related-problems

You can skip the second item (curl command output). We'll do some digging on this -- sorry for the trouble!

from honeybadger-ruby.

I will, no problem.

Thanks,
Helmy

from honeybadger-ruby.

Great thanks!

from honeybadger-ruby.