chore(deps): update dependency aio-pika to v8 #57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==7.2.0
->==8.0.0
Release Notes
mosquito/aio-pika
v8.0.0
Compare Source
Release notes
In this release, there are many changes to the internal API and bug fixes
related to sudden disconnection and correct recovery after reconnection.
Unfortunately, the behavior that was in version 7.x was slightly affected.
It's the reason the major version has been updated.
The entire set of existing tests passes with minimal changes, therefore,
except for some minor changes in behavior, the user code should
work either without any modifications or with minimal changes,
such as replacing removed deprecated functions with alternatives.
This release has been already tested in a working environment, and now it seems
that we have completely resolved all the known issues related to
recovery after network failures.
Changes:
many related problems.
UnderlayChannel
andUnderlayConneciton
, this isNamedTuple
scontains all connection and channel related properties.
The
aiormq.Connection
andaiormq.Channel
objectsare now packaged in this
NamedTuple
s and can be atomically assignedto
aio_pika.Connection
andaio_pika.Channel
objects.The main benefit is the not needed to add locks during the connection,
in the best case, the container object is assigned to callee as usual,
however, if something goes wrong during the connection, there is no need to
clear something in
aio_pika.RobustConnection
oraio_pika.RobustChannel
.__init__
method is now a part of abstract classes for mostaio_pika
entities.aio_pika.Channel
and
aio_pika.Connection
. Now you can't get aaio_pika.Connection
instance from the
aio_pika.Channel
instance.occurred in one of the channels, in case the channel was waiting for a
response frame to an amqp-rpc call.
add_close_callback
andremove_close_callback
methodsin
aio_pika.Channel
.Use
aio_pika.Channel.close_callbacks.add(callback, ...)
andaio_pika.Channel.close_callbacks.remove(callback, ...)
instead.aio_pika.RobustChannel
that causeddefault_exchane
broken after reconnecting.
publisher_confirms
property ofaio_pika.Channel
is public now.get_exchange_name
is public now.a sudden disconnection.
OneShotCallback
helps, for example, to call all the closingcallbacks at the channel if the
Connection
was unexpectedly closed, andthe channel closing frame did not come explicitly.
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.