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
After updating to 0.9.0 version to avoid the problem with server closed connection close operation I've noticed that following error always occurs after protocol close operation. Seems that protocol run is called shortly after closing.
Well, it's not so much called as it's already running as a Task when the handshake is done.
Given the current "error handling" code, yes this behavior looks correct. TBH, we don't use on_error callbacks in our production code. The whole thing needs to be reworked…
After updating to 0.9.0 version to avoid the problem with server closed connection close operation I've noticed that following error always occurs after protocol close operation. Seems that protocol
run
is called shortly after closing.I'm seeing because of
on_error
callback in which I catch and log all possible amqp errors.Is this desired behavior?
The text was updated successfully, but these errors were encountered: