-
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
Spawn go daemon does not work with Node.js v9.9.0+ #223
Comments
We're already testing js-ipfsd-ctl on nodejs 9.2.0. Is there a specific version you're thinking about? |
Possibly, I'm on 9.10.0. I'll add a reproducible example when I get a sec. |
I see. I added a test-run with 9.10.0 activated (together with the old ones we're already running): https://ci.ipfs.team/blue/organizations/jenkins/IPFS%2Fjs-ipfsd-ctl/detail/master/40/pipeline/ |
Nevermind, test with just 9.10.0: https://ci.ipfs.team/blue/organizations/jenkins/IPFS%2Fjs-ipfsd-ctl/detail/master/41/pipeline |
On Jenkins (linux at least), the node-gyp builds are not even working properly: https://ci.ipfs.team/blue/organizations/jenkins/IPFS%2Fjs-ipfsd-ctl/detail/master/41/pipeline/13 |
Taking a look now as well. |
BTW - everything up until 9.8.0 seems to work as expected (I'm on 9.0.0 myself), v9.10.0 is pretty broken. |
This is probably related to jbenet/node-subcomandante#6 |
We just published v1.2.0 for node-subcomandante, which should fix this issue. I ran the tests locally, but am running into what I believe is a type check issue when running |
This resolves down into:
Both of these packages check blocks differently, so they are not compatible. Downgrading the |
Weird this would show only under v9.9.0? I've seen the block error pop up with previous versions. Does using the correct dependencies (npm link?) fix the issue as well? |
Sorry if this was confusing. The block error has nothing to do with Node.js v9.9.0 or Everything works correctly in Node.js v9.9.0 if I downgrade |
@travisperson oh! Got you, thanks for clarifying - this makes sense then 👍 |
@alanshaw can i close this? jenkins is running node 10 and tests are passing |
.spawn
never calls back.The text was updated successfully, but these errors were encountered: