Log Message:
py-kombu: updated to 4.3.0

4.3.0:
- Added Python 3.7 support.
- Avoid caching queues which are declared with a TTL.
  Queues that are declared with a TTL are now also be excluded from the
  in-memory cache in case they expire between publishes on the same channel.
- Added an index to the Message table for the SQLAlchemy transport.
  The index allows to effectively sorting the table by the message's timestamp.
- Added a timeout that limits the amount of time we retry
  to reconnect to a transport.
- :class:celery.asynchronous.hub.Hub is now reentrant.
  This allows calling :func:celery.bin.celery.main to revive a worker in
  the same process after rescuing from shutdown (:class:SystemExit).
- Queues now accept string exchange names as arguments as documented.
  Tests were added to avoid further regressions.
- Specifying names for broadcast queues now work as expected.
  Previously, named broadcast queues did not create multiple queues per worker.
  They incorrectly declared the named queue which resulted in one queue per
  fanout exchange, thus missing the entire point of a fanout exchange.
  The behavior is now matched to unnamed broadcast queues.
- When initializing the Redis transport in conjunction with gevent
  restore all unacknowledged messages to queue.
- Allow :class:kombu.simple.SimpleQueue to pass queue_arguments to Queue object.
  This allows :class:kombu.simple.SimpleQueue to connect to RabbitMQ queues with
  custom arguments like 'x-queue-mode'='lazy'.
- Add support for 'rediss' scheme for secure Redis connections.
  The rediss scheme defaults to the least secure form, as
  there is no suitable default location for ca_certs. The recommendation
  would still be to follow the documentation and specify broker_use_ssl if
  coming from celery.
- Added the Azure Storage Queues transport.
  The transport is implemented on top of Azure Storage
  Queues. This offers a simple but scalable and low-cost PaaS
  transport for Celery users in Azure. The transport is intended to be
  used in conjunction with the Azure Block Blob Storage backend.
- Added the Azure Service Bus transport.
  The transport is implemented on top of Azure Service Bus and
  offers PaaS support for more demanding Celery workloads in Azure.
  The transport is intended to be used in conjunction with the Azure
  CosmosDB backend.
- Drop remaining mentions of Jython support completely.
- When publishing messages to the Pidbox, retry if an error occurs.
- Fix infinite loop in :method:kombu.asynchronous.hub.Hub.create_loop.
- Worker shutdown no longer duplicates messages when using the SQS broker.
- When using the SQS broker, prefer boto's default region before our hardcoded \ 
default.
- Fixed closing of shared redis sockets which previously caused Celery to hang.
- the Pyro_ transport (:mod:kombu.transport.pyro) now works with
  recent Pyro versions. Also added a Pyro Kombu Broker that this transport
  needs for its queues.
- Handle non-base64-encoded SQS messages.
- Move the handling of Sentinel failures to the redis library itself.
  Previously, Redis Sentinel worked only if the first node's sentinel
  service in the URI was up. A server outage would have caused downtime.
- When using Celery and the pickle serializer with binary data as part of the
  payload, UnicodeDecodeError would be raised as the content was not utf-8.
  We now replace on errors.
- Allow setting :method:boto3.sqs.create_queue Attributes via transport_options.
- Fixed infinite loop when entity.channel is replaced by revive() on connection
  drop.
- Added optional support for Brotli compression.
- When using the SQS broker, FIFO queues with names that ended with the 'f' letter
  were incorrectly parsed. This is now fixed.
- Added optional support for LZMA compression.
- Added optional support for ZStandard compression.
- Require py-amqp 2.4.0 as the minimum version.
- The value of DISABLE_TRACEBACKS environment variable is now respected on \ 
debug, info
  and warning logger level.