-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node inspector doesn't work: address already in use #202
Comments
Unfortunately, thats a known (and annoying ) issue. debugging doesn't work with forked processes in nodejs - nodejs/node#9435 |
Ahh... Do you know any workarounds? Like this one askmike/gekko#1666? |
@shumkov Interesting, thanks for pointing that one out - it's worth a try for sure. Would you feel comfortable sending a PR that fixes this? |
I just ran into this issue and didn't know there was already one open. I'll do a PR soon. |
When running a script that involves `ipfsd-ctl` and you pass on additional parameters it used to pass on those parameters to the subprocesses it spaws. This lead to issues especially with `--inspect-brk` as it would spawn another inspector which then would fail because there is already one running on the same port. Fixes #202.
When running a script that involves `ipfsd-ctl` and you pass on additional parameters it used to pass on those parameters to the subprocesses it spaws. This lead to issues especially with `--inspect-brk` as it would spawn another inspector which then would fail because there is already one running on the same port. Fixes #202.
When running a script that involves `ipfsd-ctl` and you pass on additional parameters it used to pass on those parameters to the subprocesses it spaws. This lead to issues especially with `--inspect-brk` as it would spawn another inspector which then would fail because there is already one running on the same port. Fixes #202.
Hello guys, thank you for your amazing work.
I use
ipfsd-ctl
for spawning IPFS instance in mocha test in a very similar way as in OrbitDb tests.It's cool but it doesn't work with node inspector:
The text was updated successfully, but these errors were encountered: