bug: pass Conn.connection_parameters to pika.BlockingConnection #80
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.
Linear Issue
N/A
Changes
__init__
s to pass the right argument type topika.BlockingConnection
.Explanation
The rabbitmq class property
Conn
has a propertyconnection_parameters
that transforms the NamedTuple that a caller would have created into apika.ConnectionParameters
whichpika.BlockingConnection
expects. However, we forgot to use this transformation throughout rabbitmq_utils.py.For example, passing an
Conn
instance toPublisher()
was throwing an uncaught exception:because the actual Conn (type: NamedTuple) was being passed to
pika.BlockingConnection
.