Matt Broadstone

@ajukraine you should be able to check the type of the `message.body` in your `received` handler

@ajukraine I'm able to confirm this locally, researching the cause of the bug at the moment.

@ajukraine so I've put together a similar test using our CI's EventHub setup, running this code: https://gist.github.com/mbroadst/6add091dea7ebea97236b0fc0a5b98da the results for both tests are as follows: ``` mbroadst@retinoid:node-amqp10 (master=)$ node 284-eh.js...

@sebastus seems like it could be related to #295 . I have a branch `issue295` where I've committed some potential fixes, if you'd care to test that branch out it...

@Romanx I'm currently merging in more fine-grained control for message disposition. Currently merged in to master is support for automatic and manual disposition. You can see some examples [here](https://github.com/noodlefrenzy/node-amqp10/blob/master/test/integration/qpid/disposition.test.js). Currently...

@Romanx ReceiverLink and SenderLinks have been implemented in master, it would be great to get some feedback on what kind of API you would want to see there (as we...

@Romanx for an example of manual disposition you can take a look at the disposition.test.js in the QPID integration tests

closing until more data comes in, this should be fixed in the 2.0.x releases

@Romanx if you are set up for manual disposition then you _must_ manually settle the incoming messages in all cases. I'm not sure what you're talking about with "deliberately threw...

@Romanx yeah okay that's what I thought you meant. @noodlefrenzy we can pop a try/catch around the call to the callback on the `ReceiverLink` and take some sort of default...