Bugsnag 4.0.0 broke error reporting

[vincentwoo]

Post 4.x upgrade, I'm not getting new bugsnag notifications for errors. Scheduling a test message works, but normal errors do not. I see errors as usual in the logs, however:

Mar 20 02:12:41 CoderPad app/web.2:  ActionView::Template::Error (undefined method `organization' for nil:NilClass): 
Mar 20 02:12:41 CoderPad app/web.2:      12:       <input id="name-prompt" placeholder="Erlich Bachman"> 
Mar 20 02:12:41 CoderPad app/web.2:      13:       <button id="go" class="btn btn-primary">Go!</button> 
Mar 20 02:12:41 CoderPad app/web.2:      14:  
Mar 20 02:12:41 CoderPad app/web.2:      15:       <% if (org = @pad.user.organization) %> 
Mar 20 02:12:41 CoderPad app/web.2:      16:         <div class="horizontal-separator">or</div> 
Mar 20 02:12:41 CoderPad app/web.2:      17:  
Mar 20 02:12:41 CoderPad app/web.2:      18:         <% session[:previous_url] = request.fullpath %> 
Mar 20 02:12:41 CoderPad app/web.2:    app/views/pads/show.html.erb:15:in `_app_views_pads_show_html_erb___336180408460726354_70203316415320' 
Mar 20 02:12:41 CoderPad app/web.2:    config/initializers/url_sanitizer.rb:25:in `call' 

however i do not see a corresponding new entry in my bugsnag dashboard. this is very alarming!

[kattrali]

Hi @vincentwoo, I'm taking a look and having trouble reproducing the issue. I created an example Rails 4.2.6 project configured to be run via rackup and then throw a similar error when the application index is loaded.

• Gemfile.lock
• crashing template

Can you provide some additional information such as the Gemfile.lock or perhaps any recently changed dependencies? The Bugsnag gem has no dependencies of its own but maybe its an interaction with something else. There are few changes between 3.0.0 and 4.0.0, the major version change being necessary only because of dropping Ruby 1.8 support.

[kattrali]

Released 4.0.1 with a possible fix for this, closing unless there is additional information.

[lonre]

4.0.1 still have this issue

[kattrali]

@lonre Can you send an example of an error or sample application to reproduce the issue to [email protected] (to avoid publicly posting sensitive information)? Alternately I'm available to chat via IRC in #bugsnag on freenode.

[lonre]

@kattrali Hi, I have report to [email protected], please check that, thanks

[kattrali]

Thanks, @lonre! The error report revealed the underlying issue. Patching in #291.

[vincentwoo]

for some reason I can't install 4.0.2, is anyone else having this problem?

$ bundle update bugsnag | grep bugsnag
Using bugsnag 4.0.1

edit: nvm, was a bundler issue