"DEPRECATION WARNING: alias_method_chain is deprecated" just after receving "ready to catch errors" #464
Description
I use this gem in a Rails 5.0.0.beta2 project, running on Heroku on Ruby 2.2.3. I used the most basic setup (just added the gem in my Gemfile and set the SENTRY_DSN env var).
Right after booting my server (or my background worker), I see this in my logs:
2016-02-20T17:53:43.781246+00:00 heroku[web.1]: Starting process with command `bundle exec puma -C config/puma.rb`
2016-02-20T17:53:46.124729+00:00 app[web.1]: [3] Puma starting in cluster mode...
2016-02-20T17:53:46.124754+00:00 app[web.1]: [3] * Version 2.16.0 (ruby 2.2.3-p173), codename: Midwinter Nights Trance
2016-02-20T17:53:46.124755+00:00 app[web.1]: [3] * Min threads: 5, max threads: 5
2016-02-20T17:53:46.124757+00:00 app[web.1]: [3] * Process workers: 2
2016-02-20T17:53:46.124760+00:00 app[web.1]: [3] * Preloading application
2016-02-20T17:53:46.124756+00:00 app[web.1]: [3] * Environment: production
2016-02-20T17:53:47.026783+00:00 app[web.1]: ** [Raven] Raven 0.15.5 ready to catch errors
2016-02-20T17:53:47.066089+00:00 app[web.1]: DEPRECATION WARNING: alias_method_chain is deprecated. Please, use Module#prepend instead. From module, you can access the original method using super. (called from block in tsort_each at /app/vendor/ruby-2.2.3/lib/ruby/2.2.0/tsort.rb:226)
2016-02-20T17:53:47.460676+00:00 app[web.1]: [3] Use Ctrl-C to stop
2016-02-20T17:53:47.465646+00:00 app[web.1]: [3] - Worker 1 (pid: 10) booted, phase: 0
2016-02-20T17:53:47.460514+00:00 app[web.1]: [3] * Listening on tcp://0.0.0.0:41623
2016-02-20T17:53:47.464741+00:00 app[web.1]: [3] - Worker 0 (pid: 6) booted, phase: 0
2016-02-20T17:53:47.917513+00:00 heroku[web.1]: State changed from starting to up
My guess is this deprecation warning comes from the Raven gem, since it's being output right after it. I mention that before having this gem I didn't encounter such warning.
Thanks