shasum failure on npm install

[rcs]

I'm seeing shasum failures when trying to npm install.

npm http GET https://registry.npmjs.org/grunt-responsive-images
npm http 304 https://registry.npmjs.org/grunt-responsive-images
npm http GET https://registry.npmjs.org/grunt-responsive-images/-/grunt-responsive-images-0.0.6.tgz
npm http 200 https://registry.npmjs.org/grunt-responsive-images/-/grunt-responsive-images-0.0.6.tgz
npm ERR! Error: shasum check failed for /var/folders/3q/bmxmmxrd4w961pksb3yv9fbm0000gn/T/npm-99596/1385865783823-0.2726634875871241/tmp.tgz
npm ERR! Expected: 313e82e3ef9dc07d15409eea1b12b25448d2cce0
npm ERR! Actual:   e74135ce47e851b3be11716fad1e068b06593be7

When manually downloading that file and running shasum on it, I sure do get 'e741..' instead of the '313e...' specced in the registry.

bash-3.2$ wget  https://registry.npmjs.org/grunt-responsive-images/-/grunt-responsive-images-0.0.6.tgz --no-check-certificate
--2013-11-30 18:48:55--  https://registry.npmjs.org/grunt-responsive-images/-/grunt-responsive-images-0.0.6.tgz
Resolving registry.npmjs.org... 67.228.31.147, 67.228.31.146
Connecting to registry.npmjs.org|67.228.31.147|:443... connected.
WARNING: cannot verify registry.npmjs.org's certificate, issued by ‘/C=US/ST=CA/L=Oakland/O=npm/OU=npm Certificate Authority/CN=npmCA/emailAddress=i@izs.me’:
  Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 200 OK
Length: 10516177 (10M) [application/octet-stream]
Saving to: ‘grunt-responsive-images-0.0.6.tgz’

100%[==================================================================================================================================================================>] 10,516,177   170KB/s   in 65s

2013-11-30 18:50:01 (159 KB/s) - ‘grunt-responsive-images-0.0.6.tgz’ saved [10516177/10516177]

bash-3.2$ shasum grunt-responsive-images-0.0.6.tgz
e74135ce47e851b3be11716fad1e068b06593be7  grunt-responsive-images-0.0.6.tgz

[andismith]

Hey,

Are you still seeing these problems? I've just tried a fresh install and it worked fine.

If it still doesn't work, can you type nvm ls in the Terminal and paste your output?

Thanks, Andi

[rcs]

Problem still seems to exist.

$ nvm ls
v0.8.7  v0.8.14 v0.8.18 v0.8.21 v0.9.12 v0.10.0 v0.10.4 v0.11.8
current:    v0.10.4
default -> 0.10 (-> v0.10.4)

Same results after an npm cache clear.

Is the sha correct? Do you get the 313.. when you download manually? Or am I getting bad results from the npm registry?

[andismith]

Do other npm packages install ok?

Are you behind a proxy? Have you taken a look at: http://stackoverflow.com/questions/13913941/how-to-fix-ssl-certificate-error-when-running-npm-on-windows

Also, if anyone else is having this problem, please speak up?

The only other thing I can think to try is to release a 0.0.7 and see if that fixes it?

[rcs]

Other npm packages install fine.

I'm not behind a proxy.

SSL errors don't seem to be the problem.

The npm registry tells me this:

$ npm info grunt-responsive-images
[...]
dist:
   { shasum: '313e82e3ef9dc07d15409eea1b12b25448d2cce0',
     tarball: 'http://registry.npmjs.org/grunt-responsive-images/-/grunt-responsive-images-0.0.6.tgz' },

Saying that that tarball should have the checksum of '313..' . Does that match your experience? Is that the same info that the NPM repo is telling you?

Fetching registry.npmjs.org/grunt-responsive-images/-/grunt-responsive-images-0.0.6.tgz over http or https both give me a tarball with a shasum of 'e74135ce47e851b3be11716fad1e068b06593be7'. Is that the same for you?

[andismith]

Ok, I'm seeing the same problem. I'll release a 0.0.7 and we'll see if the problem remains.

[andismith]

Ok, 0.0.7 has been released. Please try that.

[rcs]

Looks good to me. Do you think this was an upload that failed for some reason? I'd love to know so it can be debugged more easily by me in the future.

[andismith]

I can only think it was a bad upload to npm. I'm currently living in hotels with patchy broadband - so it could completely be my hotel Internet connection.