TrasherDK

@fernandocanizo While the scenario you describe is 100% correct, you can also have a scenario where `doSomething().then().then().catch().finally()` makes sense. A sequence where actions are dependent on the result of the...

I have absolutely nothing against `async/await` and consistency is a good thing. Don't get me wrong. What I'm trying to say, is that the task at hand should determine what...

@rooton You can find a bunch of examples: [Suggested handleUpgrade and connection flow](https://github.com/trasherdk/ws/discussions/7)

Well, if there is only one exclusive node, it makes little sense. If it's one in a list, and it start to misbehave, it makes more sense. ``` --add-exclusive-node arg...

So, even if you know you get bad information, just roll with it? Maybe the banning thingy need a review.

Mature / Stable (express ahem ahem) :laughing:

https://www.npmjs.com/package/@faker-js/faker

The solution suggested by @ioneyed seems reasonable: ```js start() let startAttempts = 0; { if (err.code === 'EADDRINUSE') { start(SERVER_PORT + startAttempts++) } }) ```

Fork on github, make changes on your fork, make pull request from your fork to here :)

How about `workLoad = docArray.length / os.cpus().length` :smiley: