Author: Colin Watson
Revision Date: 2022-10-24 05:44:46 UTC

Release 0.2.0.

Author: Colin Watson
Revision Date: 2019-05-22 08:56:20 UTC

Handle AMQP channel errors (particularly NotFound) in the publisher.

amqp 2.4.0 included a change to drain events before publishing. This
means that if we try to publish an OOPS to a nonexistent exchange, then
some future publishing attempt will raise a NotFound exception, which is
a channel error rather than a connection error and so wasn't previously
handled.

To try to minimise confusion resulting from this (which can be
considerable - it took me several days to track down what was happening
in Launchpad's test suite), spend a short time waiting for a response
for the broker after publishing an OOPS. This will typically allow us
to detect channel errors immediately, which we now handle; even if we
don't manage to handle them immediately, they'll be handled the next
time we try to publish something on the same channel.

It would be possible to handle channel errors more economically by just
reopening a channel on the same connection rather than reopening the
entire connection, but reopening the connection seems to work well
enough for now.

Author: Robert Collins
Revision Date: 2012-08-10 03:00:29 UTC

Encode the version constraint for oops in setup.py.

Author: James Westby
Revision Date: 2013-03-11 20:24:05 UTC

Merge trunk.

Author: Robert Collins
Revision Date: 2011-10-27 03:36:02 UTC

Handle amqplib's internal IOErrors.