零Rei

To work properly, `async-listener` needs to monkeypatch everywhere that a user expects a call chain to continue but the stack is going to be reset (@jacobgroundwater came up with idea...

Hey, Brian! I didn't mean browser APIs, although @Raynos's list is pretty exhaustive. I was more responding to the fact that the last time I looked at zone.js you were...

Thanks for this patch! Unfortunately, some of your new tests aren't passing: ``` not ok test/double-calls-to-create-if-importing-domain-after-async-listener.tap.js 0/4 Command: "/usr/local/bin/iojs double-calls-to-create-if-importing-domain-after-async-listener.tap.js" TAP version 13 not ok 1 number of calls to...

True enough, and they're only structured the way they are because CLS came before `async-listener`. You're working with this stuff more frequently than I am right now -- do you...

Sorry we left this sitting so long; I'll take a look at freshening and landing it (finally).

Because the idea is to separate your diagnostic output from your program's expected output – `console.log` and `console.error` print their results to different file descriptors (`stdout` and `stderr`, respectively). Is...

Thanks! Once I get back to a machine with Windows on it I'll fix this.

This is probably a job for `emitter-listener` (or it could be `events-intercept`, if that's significantly simpler). The tricky part is that the performance hit if you wrap every socket would...

This is probably going to take some `emitter-listener` levels of monkeypatching to work around, although I doubt there's any way it can be more complicated than what I had to...

I'll take a look. It's possible there's something wacky with native bindings going on under the hood and the default wrapping method won't work for zlib. Thanks for the report!