Replies: 1 comment
-
Hmm, managed to catch it, very tricky one: The exchange field in a basic.deliver frame must be a binary string, not an internal resource tuple.
Maybe I could add a catch clause for this case so others don't waste hours debugging this... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
I'm writing a simple plugin for the OCPP protocol, very similar to
rabbit_web_mqtt
, since it handles the data over websocket as well and I got into a problem I can't fix no matter how many hours I try, please help an Erlang beginner 🙂Reproduction steps
mc
pattern to build themc_ocpp
resource.rabbitmq-server/deps/rabbit_common/src/rabbit_binary_generator.erl
Line 226 in a43e2c5
but it's not so helpful, as I still can't understand where the
badarg
comes from...Expected behavior
Explicit stack trace to where the error happens in AMQP framing or where the bad argument error is thrown.
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions