Command-line arguments don't override config file weighted/ordered queues setting

[nate00]

Usually, if a setting appears in both the config file and the command-line arguments to the sidekiq command, the command-line argument takes precedence. This doesn't happen in the case of the implicit weighted/ordered queues setting, however.

In a new Rails app, if config/sidekiq.yml contains

---
:queues:
  - ['foo', 1]
  - ['bar', 1]

and I run bundle exec sidekiq -q foo -q bar, I expect Sidekiq to execute jobs from bar only when foo is empty. Instead, the worker randomly takes jobs from foo and bar.

[nate00]

(In my case, I didn't actually need any settings from the config file, so adding a --config NONE argument sufficed as a workaround.)

[mperham]

I think your expectation is correct.

[eabrahamsen-handy]

Took a look at this bug. How would we want to handle queue priorities when the number of queues on the CLI is greater than 10? My initial hunch is to start the implied weight at 10 and drop to 1; then any queue after 10 default to 1. Sound about right?

[mperham]

Either the weight is specified or it is 1.

[mperham]

No plans to fix.

[patbl]

In Sidekiq 6, the --config NONE trick stops working and you get the error ArgumentError: No such file NONE. (This is the PR responsible for that change.) We're working around this by specifying an empty file as the config file.