defunkt/resque — pull request #610 by alindeman (2012-06-06 02:59:49+00:00)
Title: Workers started with QUEUE=* do not cause error when there are no queues

* This should rarely happen (if at all) in production, but in
development, we ran into annoying situations if Redis were cleared and
we tried to start a catch-all Resque worker (via Foreman).
* The worker that is started will not process jobs, but at least it will
not die immediately with a bad exit code (which would stop all
processes in Foreman, for instance).

Before pull request:

```
[resque] QUEUE=* rake resque:work
rake aborted!
ERR wrong number of arguments for 'blpop' command
```

/cc: @tenderlove (for real this time!)