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
The streadway/amqp client doesn't err out or terminate the channel when publishing to an exchange resource that should be not found. Although one could argue the language is attempt to publish making it ambiguous. I am not sure how we would do that other than caching the full active topology queried from the server.
Work around is to declare resource and perform any bindings before using it obviously. This was obviously a developer's mistake, but noticed that it should be sending an error to give feedback to the user.
The text was updated successfully, but these errors were encountered:
This doesn't appear to be working per the spec.
The streadway/amqp client doesn't
err
out or terminate thechannel
when publishing to an exchange resource that should be not found. Although one could argue the language is attempt to publish making it ambiguous. I am not sure how we would do that other than caching the full active topology queried from the server.The above
exchange
does not exist, Mandatory/Immediate flags are both false here, but same result on true. Does not returnerr
.original source:
https://github.com/houseofcat/turbocookedrabbit/blob/110270e1131d6948d2090fa592ed0c4cb24fea8c/v2/tests/main_publisher_test.go#L76
relatable issue from my repo:
houseofcat/turbocookedrabbit#15
Confirmed on Server v3.8.7 / 3.8.14.
Work around is to declare resource and perform any bindings before using it obviously. This was obviously a developer's mistake, but noticed that it should be sending an error to give feedback to the user.
The text was updated successfully, but these errors were encountered: