Using return in Async handlers logs entire response object to stdout about node-restify HOT 4 OPEN

Is there any news on this issue? I'm considering downgrading again because of this.. :/
I think this dump was introduced in v9.

from node-restify.

I'm experiencing the same issue. Two possible workarounds are:

1. Explicitly setting req.log = null in the handler. This is obviously not ideal if you actually want to use the logging plugin for the request.
2. Moving the empty return onto a separate line after the res.send() call. Obviously not ideal either if you actually want to pass a value into the next handler in the chain.

from node-restify.

Is it a reasonable change to test if value is an instanceOf ServerResponse? If it is, don't include it in the log. Or perhaps don't log value?

from node-restify.

I'm experiencing the same issue. Two possible workarounds are:

1. Explicitly setting req.log = null in the handler. This is obviously not ideal if you actually want to use the logging plugin for the request.
2. Moving the empty return onto a separate line after the res.send() call. Obviously not ideal either if you actually want to pass a value into the next handler in the chain.

On #1 here, I ran into an issue where the in-build Restify throttle uses req.log.trace and throws an error, obviously not ideal to be removing something that is expected to be there. I've restored to #2 which is not ideal.

from node-restify.