Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Memory channel doesn't clear queues on close

See original GitHub issue

https://github.com/celery/kombu/blob/cbd327dc3bdd124c1bc4fc3d8f2b451fd10e2da6/kombu/transport/memory.py#L59

queue.empty() doesn’t empty the queue - it returns a boolean stating whether the queue is empty. In order to clear a queue (without touching the internals), one has to pop from it until it’s empty.

It remains a question if clearing should take place at all and whether the queues should be channel-scoped or transport-scoped. There’s definitely a need to be able to clear the queues between tests.

Issue Analytics

State:
Created 4 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

karolinepaulscommented, Feb 4, 2020

@auvipy There is no fix because I don’t know what the expected behaviour is.

It remains a question if clearing should take place at all and whether the queues should be channel-scoped or transport-scoped. There’s definitely a need to be able to clear the queues between tests.

It is crucial to decide on the behaviour wanted before commencing implementation.

0reactions

thedrowcommented, Mar 25, 2021

If you purge the queue using RabbitMQ, it is purged for all channels, right?