Guillaume Loulier

Hi 👋🏻 As `SchedulerBundle` and the related PR has been linked, some informations about the related "solutions" and some assertions that you made: > The existing solutions (https://github.com/symfony/symfony/issues/39719, [2](https://github.com/Cron/Symfony-Bundle), more?)...

Hi 👋🏻 I can confirm the issue of @hawkesburygeek, in my case, I'm facing the issue when using Docker, if I decide to use the Symfony CLI, no issues but...

Yes, sorry for the context that I gave, when I first tried the `symfony/demo`, it was with the Symfony CLI then I've faced the same issue as the one described...

> Well, if you are not on the latest version of a tool, updating it is a prerequisite before reporting issues (as they might be fixed already). As it wasn't...

Hi @stevro 👋 I've found a solution by overriding the `after_*` event and lopping through every items which is handled for the position attribute and setting the value to the...

I'll be glad to help bringing new features/maintaining existing extensions 🙂

Hi @jvancoillie 👋🏻 Still this issue interesting in your current usages (if you still use this bundle)? Thanks 🙂

Hi @aesislabs 👋🏻 Thanks for the interest on this PR, it's planned to be merged in `0.7`, I need to finish the implementation and work on performances 🙂

Hi @checkphi 👋🏻 Yes, all tasks are executed sequentially, to be honest, Messenger cannot natively consume messages in parallel so IMHO, there's no benefit of working on something related to...

Thanks to Supervisord, you can trigger multiple worker (same concept applies to this bundle), each worker will consume messages available at the moment. > In other words, if we start...