You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to use twingly-amqp in Wally, I happened to notice that we always need to ack our messages, I don't think it necessarily makes sense to require acking when working with the RPC aspect of RabbitMQ.
The text was updated successfully, but these errors were encountered:
This is also a problem when implementing a RPC client, the reply-to queue may not use manual ack, leads to PRECONDITION_FAILED - reply consumer cannot acknowledge (Bunny::PreconditionFailed).
I am trying to use
twingly-amqp
in Wally, I happened to notice that we always need to ack our messages, I don't think it necessarily makes sense to require acking when working with the RPC aspect of RabbitMQ.The text was updated successfully, but these errors were encountered: