Anna Henningsen

> > I would be reluctant to put a lot of effort into improving performance of a feature when there's a better, faster language built-in already available. We probably should...

> "Soft deprecate" buffer.slice and recommend .subarray() much more strongly. Yes please :) > 1. Also keep in mind that it's trivial to create a Buffer from a Uint8Array. e.g....

@jasnell That’s a bug then :)

@syg I am personally fine with anything here. `--trace-atomics-wait` has been useful for me in the past occasionally, and the thing about it is that it’s useful specifically in situations...

@pprindeville ABI-breaking changes like this should target `master`, yes. > I've not tested on Solaris or Windows. If someone could test those that would be great... CI: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/1061/ (heads up…...

Not a bug in Node.js. :) Quoting the Worker threads documentation: > Native add-ons can only be loaded from multiple threads if they fulfill [certain conditions](https://nodejs.org/api/addons.html#addons_worker_support). In short, your addon...

@reconbot You can probably use Node’s `GetCurrentEventLoop()` and `AddEnvironmentCleanupHook()`/`RemoveEnvironmentCleanupHook()` functions to achieve what you need – I don’t think there are NAN wrappers for them, though.

@TheAlphaNerd as far as yargs is concerned, https://github.com/yargs/yargs/pull/597 should take care of it. Having pty support in citgm might be still nice to have, though.

Is there anything I could do to help here?

This problem is, in fact, not really related to node-coveralls; The relevant line here is `No coverage information was collected, exit without writing coverage information`, meaning that istanbul failed to...