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
#2990, it's fair to say, is not a universally loved change; for myself, it kind of breaks our whole program 😢.
One compromise I believe makes sense, is to allow consumer_timeout to be set by the consumer, as part of the connection URI (preferably allowing for false), since it seems reasonable the client should have a say in how long it may take to complete a task.
I will convert this issue to a GitHub discussion. Currently GitHub will automatically close and lock the issue even though your question will be transferred and responded to elsewhere. This is to let you know that we do not intend to ignore this but this is how the current GitHub conversion mechanism makes it seem for the users :(
#2990, it's fair to say, is not a universally loved change; for myself, it kind of breaks our whole program 😢.
One compromise I believe makes sense, is to allow
consumer_timeout
to be set by the consumer, as part of the connection URI (preferably allowing forfalse
), since it seems reasonable the client should have a say in how long it may take to complete a task.See: https://www.rabbitmq.com/uri-query-parameters.html#tls
Originally posted in #2990 (comment)
The text was updated successfully, but these errors were encountered: