Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update asynqp to v0.4 #1

Open
wants to merge 146 commits into
base: master
Choose a base branch
from

Conversation

umamaistempo
Copy link

No description provided.

Benjamin Hodgson and others added 30 commits March 27, 2015 13:24
Update README.md according to #9
automatically reconnect on a lost connection

Added ConnectionClosedError and ConnectionLostError.
ConnectionClosedError is raised when the connection is closed normally,
ConnectionLostError is raised when the connection is lost unexpectedly.
cleanup
Send poison pill when the connection is closed so that cleanup methods
(Channel.close, Connection.close, Consumer.cancel) do not block waiting
for a message from the server on a closed connection.
Fixes from experience with an actual example script
consistently handle setting futures inside syncronizer when poison pill
is swallowed
Added new exceptions and logic to allow reconnecting connections
Stop squashing OsError into ConnectionRefusedError when connecting
Explicitly use unsigned serialization for unsigned integers
Expand table serialization for more types (integers, bool, dict)
Signed/unsigned serialization and expanded table serialization
tvoinarovskyi and others added 30 commits March 20, 2016 12:46
Correctly handle zero-length messages
Fixed amqp properties reading. Had invalid flag checks.
Added v0.5 changes and fixed conformance doc page
Changed the reconnect example to show new features in 0.5
Added backward compatible closed future.
…ext manager (#81)

* changed all "try except pass" occurences to suppress context manager

* typo fix

* removed unused import
* ADD: connection close callback feature

* FIX: forgoten return
I spent a while digging around in the source before I found that one gets to handle unpublishable messages by setting a return handler on the channel.  A link from publish to that method would have saved me a lot of time :)
)

* fix asyncio.async deprecation warning (replaced with ensure_future)

* fix indentation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.