forked from benjamin-hodgson/asynqp
-
Notifications
You must be signed in to change notification settings - Fork 0
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
umamaistempo
wants to merge
146
commits into
HackerExperience:master
Choose a base branch
from
benjamin-hodgson:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
Example/reconnecting socket
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
Correctly handle zero-length messages
Added server side consumer cancel
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 :)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.