tiny-worker: Error when running Node in debug mode

If I try to use this module with Node in debug mode (started with node --debug --nolazy ./index.js) I get the following error:

Error: listen EADDRINUSE :::5858
    at Object.exports._errnoException (util.js:1012:11)
    at exports._exceptionWithHostPort (util.js:1035:20)
    at Agent.Server._listen2 (net.js:1252:14)
    at listen (net.js:1288:10)
    at net.js:1398:9
    at _combinedTickCallback (internal/process/next_tick.js:77:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 20 (11 by maintainers)

Most upvoted comments

I know, I’ve read the code before opening this issue. I’m not here to waste my time, and yours neither.

Just change this line to:

this.child = fork(worker, [], {execArgv: []});

and it’s fixed.

And as a personal suggestion: stop being a dick with the people who contribute to improve your work.

danieleds on Oct 7, 2016

There is a caveat, because this is not in the ctx most people assume the default cwd is of the process that spawns the worker. It’s not possible to solve it in such a way that works for everyone without removing the vm context which kinda breaks the API and would be a value hit.

avoidwork on Mar 27, 2017

Yeah; all you ever had to do was open a PR with the feature you wanted to add.

https://github.com/avoidwork/tiny-worker/commit/a63db63a3a8437315fa70e56bbb99ccca18e378f

I accept ownership of bugs I produce, & I will argue default behavior. I don’t even lock threads, because I find there’s value over time revisiting requests or problems people bring my attention to, such as this one. You were I believe the first of 3 distinct asks, third strike (against the lib) I added the feature.

avoidwork on Mar 27, 2017

dude, this’ll look so awesome on your profile long term.

avoidwork on Mar 27, 2017

Sure thing cowboy.

nicholaswmin on Mar 27, 2017

@nicholaswmin simmer down pot, this kettle isn’t angry. if you look at any my other projects you’ll see i welcome PRs, and tell assholes to fuck off if they blame me for something the framework does.

I’m not responsible for you guys knowing how shit works, or how to conduct yourselves such that a real contribution would be welcomed; what you did here is just reiterate the fucktard approach of blaming someone else for your problem.

avoidwork on Mar 27, 2017

What did you contribute? You ate up my time with this little thread.

Suggestion: Don’t be a bitch.

avoidwork on Oct 7, 2016