Bugsnag breaks with Sidekiq 5.0.0

[reubenbrown]

After updating sidekiq to version 5.0.0 the sidekiq process will not start due to an uninitialized constant in bugsnag.

Below is the backtrace:

There was an error while trying to load the gem 'bugsnag'.
Gem Load Error is: uninitialized constant Sidekiq::Middleware::Server
Backtrace for gem load error is:
/.rvm/gems/ruby-2.4.0/gems/bugsnag-5.3.1/lib/bugsnag/sidekiq.rb:30:in `block (2 levels) in <top (required)>'
/.rvm/gems/ruby-2.4.0/gems/sidekiq-5.0.0/lib/sidekiq.rb:143:in `server_middleware'
/.rvm/gems/ruby-2.4.0/gems/bugsnag-5.3.1/lib/bugsnag/sidekiq.rb:29:in `block in <top (required)>'
/.rvm/gems/ruby-2.4.0/gems/sidekiq-5.0.0/lib/sidekiq.rb:73:in `configure_server'
/.rvm/gems/ruby-2.4.0/gems/bugsnag-5.3.1/lib/bugsnag/sidekiq.rb:28:in `<top (required)>'
/.rvm/gems/ruby-2.4.0/gems/bugsnag-5.3.1/lib/bugsnag.rb:127:in `block in <top (required)>'
/.rvm/gems/ruby-2.4.0/gems/bugsnag-5.3.1/lib/bugsnag.rb:125:in `each'
/.rvm/gems/ruby-2.4.0/gems/bugsnag-5.3.1/lib/bugsnag.rb:125:in `<top (required)>'
/.rvm/gems/ruby-2.4.0/gems/bundler-1.14.6/lib/bundler/runtime.rb:91:in `require'
/.rvm/gems/ruby-2.4.0/gems/bundler-1.14.6/lib/bundler/runtime.rb:91:in `block (2 levels) in require'
/.rvm/gems/ruby-2.4.0/gems/bundler-1.14.6/lib/bundler/runtime.rb:86:in `each'
/.rvm/gems/ruby-2.4.0/gems/bundler-1.14.6/lib/bundler/runtime.rb:86:in `block in require'
/.rvm/gems/ruby-2.4.0/gems/bundler-1.14.6/lib/bundler/runtime.rb:75:in `each'
/.rvm/gems/ruby-2.4.0/gems/bundler-1.14.6/lib/bundler/runtime.rb:75:in `require'
/.rvm/gems/ruby-2.4.0/gems/bundler-1.14.6/lib/bundler.rb:107:in `require'
/sample_app/config/application.rb:9:in `<top (required)>'
/sample_app/config/environment.rb:2:in `require'
/sample_app/config/environment.rb:2:in `<top (required)>'
/.rvm/gems/ruby-2.4.0/gems/sidekiq-5.0.0/lib/sidekiq/cli.rb:255:in `require'
/.rvm/gems/ruby-2.4.0/gems/sidekiq-5.0.0/lib/sidekiq/cli.rb:255:in `boot_system'
/.rvm/gems/ruby-2.4.0/gems/sidekiq-5.0.0/lib/sidekiq/cli.rb:54:in `run'
/.rvm/gems/ruby-2.4.0/gems/sidekiq-5.0.0/bin/sidekiq:12:in `<top (required)>'
/.rvm/gems/ruby-2.4.0/bin/sidekiq:22:in `load'
/.rvm/gems/ruby-2.4.0/bin/sidekiq:22:in `<main>'
/.rvm/gems/ruby-2.4.0/bin/ruby_executable_hooks:15:in `eval'
/.rvm/gems/ruby-2.4.0/bin/ruby_executable_hooks:15:in `<main>'

It appears the issue is happening here because sidekiq removed server middleware
so the Sidekiq::Middleware::Server::Logging constant no longer exists (See here for more info).

Simply reverting this commit fixes the issue. I can open a pull request reflecting this change.