-
Notifications
You must be signed in to change notification settings - Fork 29
Issues: benjamin-hodgson/asynqp
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
publish does not guarantee delivery, and socket error is not raised to be handled by application
#106
opened Sep 3, 2018 by
hritik09
name q1@node or q1$node is valid by rabbitmq, but not valid by VALID_QUEUE_NAME_RE
#102
opened Feb 7, 2018 by
inshua
send to not exists routing key will raise error but cannot capture it
#101
opened Feb 7, 2018 by
inshua
Synchroniser.notify hits 'unexpected method notification' in tests.
#94
opened Feb 22, 2017 by
alexjc
It's possible to lock up queue.consume() so that it never emits any callback.
#91
opened Dec 7, 2016 by
CompPhy
ProTip!
Add no:assignee to see everything that’s not assigned.