Mark Story
Mark Story
The namespace changes are done now :smile:
@T0mats0 I think an end to end test for a successful job dispatch and execution would be great to have. The documentation has been deployed and auto updates on each...
I think we can do an initial release soon. The first batch of features are in place, and tests are much better than they were before.
Having monitoring views/controllers sounds interesting to me. I don't think any have been added this far as nobody has brought it up.
> On the receiving side (for me it's Python): it ingests from the job queue, and also checks the other queue. If the other queue contains the job ID currently...
How would someone go about reproducing the issue you're having? Are you able to reproduce this issue using a transport that isn't mongo db?
> The only way I can seem to get the jobs onto different queues is to add the queue option to the config. I think we might have an issue...
I've tracked this down to being related to how `QueueManager::push()` generates Enqueue Client instances. When a client instance is created. `Enqueue\SimpleClient\SimpleClient` will use our 'queue' configuration value to[ set the...
> When a topic has mixed queue messages ones with no matching binding are silently acked (I've not tracked where this happens yet. The output we're seeing when messages are...
From the snippet you provided your `url` is `redis:` which isn't going to work. I've not used predis before. What are its connection strings supposed to look like?