-
Notifications
You must be signed in to change notification settings - Fork 20
attach: crash if initial-delivery-count is not 0 #9
Comments
Yeah, we seem to be assuming it will be 0. That should be fixed, but in the mean time it might help you get further to set it to 0... |
Okay I've been trying to parse through this a little bit more, now it seems to me that your attach frame matcher is perhaps incorrect? If I look at the spec, the performative definition is as follows:
and yet your definition for attach is as follows:
am I missing something? |
we're actually sending initial delivery count as |
for extra help here, the js representation of the performative we are sending is:
and the raw hex is:
|
@simonmacmullen the error seems to be in lines 52-82 of rabbit_amqp1_0_incoming_link, but that's about as far as I've gotten.. I find erlang's "backtraces" somewhat difficult to parse at this point , and would be very interested to learn how you did it when you do 😄 |
@simonmacmullen are those arguments meant to line up directly with the performative description? |
@simonmacmullen lol, okay well after like an hour and a half of sifting through those 30 lines it turns out yes indeed, we are sending 1 as the initial message count and the bug is in fact that you guys assume 0.. I suppose we can chalk this up to a nice erlang learning experience! |
Thanks! |
Hey, running into another parsing error it seems. I was wondering if you could help me figure out what's going on with it from the rabbitmq side (if I can better understand why these errors are happening, I can hopefully start submitting more relevant issues 😄). The error is:
I think this might be a problem with an invalid match on initial_delivery_count? But to be frank I'm a bit lost, and trying to play catchup
The text was updated successfully, but these errors were encountered: