Ask Solem

Did you set the visibility timeout also on flower? If not it will be restoring messages at the default rate.

Closing this, as we don't have the resources to complete this task.

I'll be looking into this, but it's now better to use `connection.drain_events(timeout)` instead of channel wait. This allows you to consume events from multiple channels at a time, something that...

Btw, I'm not seeing this here, even with `channel.wait(None)`. It would be very helpful if you could write a short snippet that reproduces the issue! I guess you should try...

There's no way to do that so message handlers must return within the heartbeat interval

Right, using Async I/O would be the solution, we cannot use threads for this. I'm already working on async support so this is forthcoming, including eventual support for tulip/asyncio

Btw, it does not really help for heartbeat frame processing/sending since the 'message processing' callbacks are still the problem. I.e. if you have a callback anywhere that blocks without yielding...

My work is in the celery/py-amqp@callbacks branch, it's not finished and is cheating in a number of places but it's one hell of a medal-deserving refactoring job ;)

Thanks for looking into this! Clearly a bug I merged #55 for now as that one is easier to reason about, but hope to merge #56 as well

The program above raising CancelledError works for me, it pretty much just exits (mode master) I agree using the beacon to stop is not very great, I guess the best...