Errors in callbacks shouldn't be caught about arangojs HOT 6 CLOSED

I'm not sure I follow. What is happening and what should be happening?

from arangojs.

In node, exceptions in asynchronous code is typically bubbling up to the nearest exception handler. If there isn't a handler, the node process prints detailed information about the exception before terminating.

It seems that something in this adapter is wrapping callbacks in an exception handler. I expect my little example to terminate with a ReferenceError: programmer is not defined, but it doesn't. My callback is just ending quietly and the process continuous to run.

from arangojs.

Over the weekend, I've refactored my code from callbacks to promises, which are behaving correctly. So I'm not affected by this exceptions-in-callbacks-incorrectly-being-caught issue anymore.

from arangojs.

Which JS environment are you using? I'm guessing this problem occurs when promises are supported (e.g. latest Chrome or node 0.12) and you're using the errbacks instead.

Basically, the errback will be invoked in the promise's then method. Exceptions in that method will result in the promise returned by that method to be rejected but nothing else. As the promise is silently discarded, the error simply vanishes.

from arangojs.

I've adjusted the logic so the errback is invoked outside the promise logic. This should give you the behaviour you're expecting.

from arangojs.

iojs v2.2.1

from arangojs.