Ilan Steemers
Ilan Steemers
Thanks for asking how I'm doing. I've been offline for a while due to some real life events that I had to deal with. This has led to me not...
I actually started the process of moving to jazzband, but never got to finish it. I'll try to make some time this weekend to do some cleanup and see if...
I was ready and pumped to go, and then my entire family caught Corona. Everyone is doing fine now, I just need to find time to work on this. I...
Workers signifies the amount of multiprocessing workers per cluster instance. For Heroku you would set up a procfile with a 'worker' line. The two should not be confused. The 'worker'...
Currently there are no multiple queues. Although we do use it in testing by setting the `list_key` variable, it is not possible for the workers to read from multiple queues...
This is fairly easy to accomplish, it's just that it would also require to separate worker clusters for each queue. In fact most of the code is already in place...
I'm happy that worked out. I've been using separate queues for parallel testing mostly, until now. Let me think a bit on how to integrate this into the project. You're...
Currently on holiday, but will have a look when I'm back. Thanks for the detective work. On Thu, 30 Jul 2020, 11:59 Ikarys, wrote: > Hi, > > I have...
Yes, and the docs need to be updated too. It happened because of a recent PR. Either that or we don't show the warning on no timeout configured.
We added id defaults in 1.3.8 which is a requirement for Django 3.2. I am guessing you have a custom default type set?