Danlock

I really enjoyed the Mythical Man Month.

Yes, it's because this library doesn't take a context.Context in and actually use it to timeout AMQP call's. You can check out my [wrapper](https://github.com/danlock/rmq) which was created to solve this...

I wrote an example to demonstrate a similar problem I've had with amqp091-go (a connection hanging), with a similar solution (use contexts throughout amqp091-go). No ethernet unplugging required. https://github.com/Danlock/rmq/blob/17f5efed0a2038993f1da091398b0a174812a02a/hang_int_test.go#L29 Unfortunately...

If you look at my library danlock/rmq's implementation, it's closes the channel when there is a timeout using it, and closes the connection when there is a Channel() timeout. I...

danlock/rmq.NewConsumer() creates an auto reconnecting consumer that recreates AMQP channels as necessary. I'm not exactly sure what you are asking about, but if it's related to your usage of Danlock/rmq...

That does seem better to me, and maintaining parity with other language implementations is important. In regards to that specific edge case, if a subscription frame timed out, presumably the...