mro-rhansen2

Understood. Do you happen to know how to get in touch with that community? Their issue board is deactivated on GitHub and it doesn't appear that they have a gitter...

Thanks a million! I've reached out to their community. It appears that they are actively looking for people to give this a whirl so hopefully they will provide some feedback...

I've traced an intermittent hang in our processes to this exact same section of code. We have processes where the only thing keeping them alive is that we're consuming messages...

After further investigation, I did find another avenue where this same deadlock can occur during a `consumer.poll()`. If the timing is just right, then there's a chance that the `HeartbeatThread`...

> Dana got back to me, hold your horses folks. We're working on it. Is there any update that you can provide at this time?

> I still disagree, firstly you should not be logging the entire response in any use case ever, what should be done is you should log only the parts of...

The Kafka consumer fetch itself becomes blocked and stops producing new messages. We're using the consumer in follower mode by treating it as an iterable. That loop is the only...

Hello again! This bit us again in our current iteration so I've finally got time to muck around with this again. Thanks for the tip on disabling streaming. I didn't...

Just wanted to drop by to confirm that disabling streaming seems to have resolved the problem. It has been nearly two weeks at this point and we have not noticed...

Thanks @mredolatti, but the project that I deactivated streaming on in this case doesn't actually employ asyncio. The conflict seems to be between the kafka-python polling thread and the splitio_client[cpphash]...