Sidekiq 5.2.2 breaks GitLab.com sidekiq-cluster config
We upgraded to Sidekiq 5.2.3, which has the change in https://github.com/mperham/sidekiq/pull/3936/files (in 5.2.2). However, this is going to break our sidekiq-cluster config:
2018-11-19_21:36:16.94007 2018-11-19T21:36:16.939Z 14279 TID-oveubl9f0 INFO: A worker terminated, shutting down the cluster
2018-11-19_21:36:17.07635 2018-11-19T21:36:17.076Z 14310 TID-ox18zdg4g INFO: Starting cluster with 1 processes
2018-11-19_21:36:17.91363 queues: merge cannot be defined twice
2018-11-19_21:36:17.91366 /opt/gitlab/embedded/lib/ruby/gems/2.5.0/gems/sidekiq-5.2.3/lib/sidekiq/cli.rb:440:in `parse_queue'
2018-11-19_21:36:17.91366 /opt/gitlab/embedded/lib/ruby/gems/2.5.0/gems/sidekiq-5.2.3/lib/sidekiq/cli.rb:346:in `block (2 levels) in parse_options'
2018-11-19_21:36:17.91367 /opt/gitlab/embedded/lib/ruby/2.5.0/optparse.rb:1584:in `block in parse_in_order'
2018-11-19_21:36:17.91367 /opt/gitlab/embedded/lib/ruby/2.5.0/optparse.rb:1538:in `catch'
2018-11-19_21:36:17.91367 /opt/gitlab/embedded/lib/ruby/2.5.0/optparse.rb:1538:in `parse_in_order'
2018-11-19_21:36:17.91367 /opt/gitlab/embedded/lib/ruby/2.5.0/optparse.rb:1532:in `order!'
We should downgrade to 5.2.1 until then.
I don't think this should be enforced in Sidekiq; I'll raise an issue there: https://github.com/mperham/sidekiq/issues/4022