Gyula Szalai

Oh, I see. But this time it's not about child loggers. I have only one logger that I would like be ECS compatible. Is there any way I can solve...

@glynnbird any thoughts on this issue?

@glynnbird Isn't this issue fixed yet? #246 fixed it and is already merged.

It seems that error propagation is OK now, but after catching the error the VM doesn't exit. So there must be some unsettled promise.

@glynnbird @byronmurg Just checked the example code with `why-is-node-running` and found that the followin things prevent the VM from exiting: ``` # ZLIB /Users/gyszalai/work/github/nano9_bug/node_modules/axios/lib/adapters/http.js:213 - stream = stream.pipe(zlib.createUnzip()); # TTYWRAP...

I just dug down and found that if you don't set `maxSockets: 50` in the defaultHttpAgent options, the VM exits gracefully after receiving and logging the error from axios.

It seems that even keepAlive has to be disabled in the `defaultHttpAgent` options

I had the same problem with getting the user profile. It seems that the userinfo URL has changed as Google shuts down google+ The default userinfo URL in passport-google-oauth2 is...

If you run your application in a Docker container, make sure that your Docker default bridge is reconfigured as the default config is 172.x.x.x and in my case it conflicted...

Forgot to mention it's NetBeans 7.3 final and Ubuntu 12.10.