Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NoMethodError after updating to 6.11.1 #555

Closed
Jonathan-Arias opened this issue Jul 31, 2019 · 4 comments
Closed

NoMethodError after updating to 6.11.1 #555

Jonathan-Arias opened this issue Jul 31, 2019 · 4 comments
Labels
bug Confirmed bug released This feature/bug fix has been released

Comments

@Jonathan-Arias
Copy link

Description

I’m trying to update the bugsnag gem from 6.10.0 to 6.11.1 for a rails application and the following error started to pop up when running the test suite. I'm able to run 6.10.0 without any issues.

undefined method `each_with_object' for nil:NilClass (NoMethodError)
/gems/bugsnag-6.11.1/lib/bugsnag/integrations/railtie.rb:82:in `block in event_subscription'

Might be related to using mysql2 as discussed here.

Configuration for bugsnag is pretty minimal.

Bugsnag.configure do |config|
  config.api_key =
  config.meta_data_filters +=
  config.release_stage ||= ENV['RAILS_ENV'] || 'development'
  config.ignore_classes += [SignalException, SystemExit]
end

Environment

  • Rails 3.2.22
  • Bugsnag 6.11.1
  • mysql2 0.3.21
@mattdyoung
Copy link

Hi

Yes, it looks like it may be related to using mysql2. We'll try to see if we can resolve this in bugsnag-ruby, and let you know when we have an update.

Thanks!

@mattdyoung mattdyoung added the bug Confirmed bug label Aug 2, 2019
@phillipsam phillipsam added backlog We hope to fix this feature/bug in the future scheduled Work is starting on this feature/bug and removed backlog We hope to fix this feature/bug in the future labels Aug 2, 2019
tomlongridge added a commit that referenced this issue Sep 2, 2019
Older versions of `mysql2` adapter do not contain the `bind` key in the Active Record notification.

#555
@mattdyoung
Copy link

Fixed in v6.12.1

@mattdyoung mattdyoung added released This feature/bug fix has been released and removed scheduled Work is starting on this feature/bug labels Sep 6, 2019
@xxx44yyy
Copy link

xxx44yyy commented Mar 21, 2021

again, 6.19

@xljones
Copy link

xljones commented Mar 23, 2021

Hi @xxx44yyy, can you please let us know more detail about the error that you're seeing? Which version of Rails are you using? Is this related to mysql2 too? If so, which version are you using.

Just seen that you've raised #653, let's move discussion over to there. If you could please let us know a bit more detail about what's happening in the run up to the error, and include any Bugsnag configuration you're using.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bug released This feature/bug fix has been released
Projects
None yet
Development

No branches or pull requests

5 participants