Andreas Erhard

Thank you, I'll test the new feature and if everything works as expected I'll include it in 2.3 :smile:

Hi @MaximeMaillet! Thank you for your PR! Your current approach would prohibit the usage of Symfony 3, it should be `~2.7|~3.0|~4.0.0` instead. Or even better, just `~2.7|~3.0|~4.0` to allow 2.7...

Right, that's why the last PR integrating support for Symfony 3.x took quite some time and also manual testing effort. Having a comprehensive test suite would defintely help a lot!...

@mjphaynes What do you think about the separation of the php-resque core from the CLI? Now that Symfony 4 is entering LTS soon and 5 to be released shortly, this...

Any news @mjphaynes? As Symfony 5 is gaining traction, proper support seems to become more important for this project as well. By the way, maybe we should also re-evaluate the...

Thanks for reporting this issue, @fredams and for the quick response, @scones! Apparently, KEYS should not be used according to the Redis-Docs[1], so the Predis Library used by php-resque does...

Last week I found some interesting articles regarding Redis performance tuning where blocking vs non-blocking mode is explained in detail... I'll post the references here on monday.

@mjphaynes Should we create a `mjphaynes/php-resque-cli` repository to reduce the dependencies and move the command stuff there? Of course this would be a significant BC break and require a major...

Ah, yes of course 😀

Hi @mstra001! Thank you for reporting your issue. Apparently there is a problem with your Redis connection, which causes the worker to fail. The error message seems to indicate an...