search

duojs / duo

A next-generation package manager for the front-end
3.42k stars 118 forks source link

Unable to install duo; failed to fetch vargs from registry #494

Closed Alhadis closed 9 years ago

Alhadis commented 9 years ago

This might be the fault of the vargs maintainer, but beyond what's implied by a very absent page at NPM.js, I'm unable to find anything that'd explain why the dependency is suddenly breaking installs.

This was what was sent to STDERR after running npm -g install duo:

> leveldown@1.4.0 install /usr/local/lib/node_modules/duo/node_modules/duo-cache/node_modules/level/node_modules/leveldown
> prebuild --download

npm ERR! Darwin 13.4.0
npm ERR! argv "node" "/usr/local/bin/npm" "-g" "install" "duo"
npm ERR! node v0.12.7
npm ERR! npm  v2.13.3

npm ERR! failed to fetch from registry: https://registry.npmjs.org/vargs
npm ERR! 
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/johngardner/Desktop/npm-debug.log

I've copied the npm-debug.log to PasteBin, as the result was too big to fit in a GitHub issue.

Is this a temporary issue?

System specs

dominicbarnes commented 9 years ago

I've started seeing this on CI now, I'm not sure what's happening yet either. :\

I can't seem to reproduce locally though, which is really weird. (I'm hoping it's a transient bug, I'll report back if I discover anything)

dominicbarnes commented 9 years ago

I don't see this consistently, how about you @Alhadis ?

As best I can tell, it's a transient/temporary problem.

Alhadis commented 9 years ago

Weird. :| It appears to be working now.

It was failing repeatedly last night, I tried about three or four times between 15-minute intervals, so I was convinced it wasn't too temporary.

Strange... leaving this issue open to grant visibility to the matter, though, as the catalyst of the issue probably warrants identification.

dominicbarnes commented 9 years ago

Looks like this was an issue with the npm registry that affected very old packages. (of which vargs is one of them)