Skip to content
This repository has been archived by the owner on Jun 14, 2018. It is now read-only.

[TEST] Error: Starting inspector on [...] failed: address already in use #113

Closed
ghost opened this issue Feb 8, 2018 · 1 comment
Closed

Comments

@ghost
Copy link

ghost commented Feb 8, 2018

During work on #87 and #110, the following error came up:

Problem

  1) EthPM integration "before each" hook: Create a fake EthPM host and memory registry for "successfully installs single dependency from EthPM":
base.js:225
     Error: Starting inspector on 127.0.0.1:39487 failed: address already in use
      at Object.done (P:\sand\truffle\dependencies\truffle-core\node_modules\ipfsd-ctl\src\exec.js:23:27)
      at Stream.listeners.done.once (P:\sand\truffle\dependencies\truffle-core\node_modules\ipfsd-ctl\src\exec.js:45:18)
      at Stream.f (P:\sand\truffle\dependencies\truffle-core\node_modules\once\once.js:25:25)
      at emitOne (events.js:116:13)
      at Stream.emit (events.js:211:7)
      at Socket.reemit (P:\sand\truffle\dependencies\truffle-core\node_modules\duplexer\index.js:70:25)
      at emitOne (events.js:121:20)
      at Socket.emit (events.js:211:7)
      at Pipe._handle.close [as _onclose] (net.js:554:12)

This happens because the mocha-test launches another process (ipfs daemon), and the node.js debugger is loosing it (can't handle this by default). This was tested with VSCode and Webstorm on win10.

Workaround

This is a know issue, with several workarounds (and possibly even a solutions) written over the years on the web.

The most official workaround/solution should be selected, documented and applied.

@ghost ghost changed the title [TEST] Error: Starting inspector on 127.0.0.1:39487 failed: address already in use [TEST] Error: Starting inspector on [...] failed: address already in use Feb 8, 2018
@ghost
Copy link
Author

ghost commented Apr 7, 2018

@cgewecke , closing this for... housekeeping reasons!!!

@ghost ghost closed this as completed Apr 7, 2018
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants