Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

cb() never called! on 1.4.14 #5787

Closed
gionn opened this Issue · 14 comments

7 participants

@gionn

npm --version
1.4.14
nodejs --version
v0.10.29
Ubuntu 12.04 with chris lea ppa.

Solved with rm -fr $HOME/.node-gyp
It started happening while trying to build a postgres native library without libpq-dev installed.

https://gist.github.com/gionn/198c08b98e57f70e092c

@trashhalo

same issue with the same versions. but hit it with node-sass. occasional failure during compilation. downgraded node to 0.10.12 and it went away.

@tommymessbauer

+1

This has been intermittent, though it has become consistent tonight on CentOS. Mac OS X is still intermittent and re-running npm install on mac seems to help.

npm cache clean not helping. Same version as @gionn listed above.

@tommymessbauer

I upgraded to the following and issue is gone. Hope that helps someone.

npm version
1.4.21
node version
v0.10.30

@gionn

@tommymessbauer the ubuntu ppa recently get the same versions, still rarely occurs for me.

@backflip

In my case (0.10.28 with 1.4.14 on OS X Mavericks) it seems to be network-related somehow. Disconnecting from a VPN network "resolved" the issue (although it might have been a coincidence).

@tommymessbauer

This feels like a race condition. It had been manageably intermittent (I spoke too soon earlier) and tonight it cannot install at all on centos.

I started having the 100% failure issue on this version

npm version
1.4.21
node version
v0.10.30

Then I upgraded. Still having exact problems with this version:
npm version

1.4.23
node version
v0.10.31

Based on npm code read, the error is bubbling from a global uncaughtException somewhere. Global uncaughtExceptions are the hardest to trace and there is no stack trace to work with.

In my case, the weird thing is that it always happens after node-sass compiles and runs tests. This process can take some time so maybe there is a timeout somewhere that throws?

Anyone on the npm team have any idea here? @isaacs possibly?

@tommymessbauer

This is definitely an npm bug in 1.4.x. I cloned this repo. I performed clean checkout, npm build/install, then tried multiple passes at install with each.

  • 1.4.23
  • 1.4.24
  • master (which was 2.0.0-alpha.7, commit #dbf0cab29d0db43ac95e4b5a1fbdea1e0af75f10 at the time of running)

To run, I executed node /path/to/npm/bin/npm-cli.js i. This was performed on the same machine back to back. I cycled through the branches 2 times each to ensure that there were no build artifacts. The results below were consistent.

The 2.0.0-alpha.7 version successfully installed every time in my test.
The 1.4.2x version failed with cb() never called! every time.

@gionn

Updates just landed on the PPA repository, and I've updated to:
node v0.10.31
npm 1.4.23
and the problem is disappeared only when shrinkwrap is absent.

Edit: only now I am noticing a bunch duplicates: #5920 #5692

@vladikoff

As mentioned in #5920, Workaround is to go back to npm 1.3, i.e npm install -g npm@1.3

@tommymessbauer

@vladikoff That's helpful. Thank you.

latest 2.0.0 alpha also seems to be getting me over the hump.

@vladikoff

alpha

Yeah that's scary

@tommymessbauer

it is less scary than not being able to deploy your code.. :)

Thanks again for the tip on 1.3. If this alpha build ends up having issues, at least I have another lead on a resolution.

@vladikoff vladikoff referenced this issue in node-freight/freight-server
Closed

Update npm version #8

@jamiemccrindle

+1

npm 1.4.23
node v0.10.31

npm ERR! cb() never called!
npm ERR! not ok code 0

@othiym23
Owner

This is a duplicate #5920, which we're actively working on right now. As far as I've been able to determine, it's a bad interaction between lifecycle scripts and shrinkwrapped dependencies, but we haven't isolated the underlying cause yet.

I'm going to close this in favor of #5920, so I can keep the discussion in one place. Thanks for your patience!

@othiym23 othiym23 closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.