Benjamin Gruenbaum

The error isn't coming from the server it's coming from the request or response being closed early, you should probably add an error handler on the request/response streams as well.

Anyway this is not a bug from what I can tell - so I'll move to nodejs/help

> which is so serious that I personally think this error should have occurred in the Http2Server.on (' error ') event. But the error is part of the request stream...

Well, Anna developed a lot of the Node.js worker_threads module in Ayo which is one big one, some refactoring also ended up being merged into Node.js - also by Anna,...

@petkaantonov wrote a pull request for Node.js but got burned out on it in the middle. You can take a look at https://github.com/petkaantonov/io.js/commit/ea143f72fc6845668716bd7a5da22771011defe4

@tagkiller - we could do this two years ago https://github.com/nodejs/node/pull/1159 - the collaborator got tired of not having enough feedback from core and it eventually got closed as https://github.com/nodejs/node/pull/2133 This...

Fibers are largely superseded by async/await and solve a problem ayo doesn't really have.

Fibers are not faster, look at the benchmarks bluebird always beat fibers since 2013. Also, we should stick with standard approaches (promises/async await) rather than go against the language specification.

Actually, I want to be proven wrong here - and I want you to know you're being taken seriously here and your suggestions and feedback are welcome. Would you please:...

I ask that you moderate your comment above to use respectful language @ngot. If you would like to have meaningful and constructive discussion we're up for that.