bashirmindee

even with alphabetic characters alone, I am not able to have the queue name correctly displayed

I had queue length of the queue not showing up because I had deactivated remote control on my celery workers ([cf](https://docs.celeryq.dev/en/stable/userguide/configuration.html#worker-enable-remote-control)) However, I still have queue_name defaulting to `celery` in...

I found the problem for queue_name being displayed as celery is caused by not setting task_send_sent_event to True on the producer's end. https://docs.celeryq.dev/en/stable/userguide/configuration.html#task-send-sent-event worker_send_task_events should be enabled in the worker...

I have a similar problem. Any updates ?

I think this has already been done actually

for inputs it has already been done: https://github.com/mindee/tawazi/blob/c612d9a841420b2806b5c854e497ea3d8bcd8bb2/tawazi/_dag/dag.py#L303 However for the ouptuts it hasn't yet. I think it was a little complicated for the output because it meant exploring all...

what do you mean by that ? we are obliged to construct a new queue every time we complete the execution of a root node, because new runnable_xns_ids might be...

I think this won't be beneficial and pretty complicated TBH. Remember that the newly created root nodes are dynamic after each iteration of the scheduler; hence the number of combinaisons...

we are having the same problem with triton + kube but on grpc side. It seems that triton isn't designed to work with a dynamic number of PODs on the...

thank you for this. We tried service mesh istio but the results weren't as good as we hoped