"uid must be an unsigned int" on io.js 1.0.3 (x64) on 64-bit Windows 8.1

[mgol]

io.js 1.0.3 (x64 edition) on Windows 8.1 gives me the following errors when running npm install on https://github.com/mzgol/grunt-ng-annotate/:

C:\Users\mgol\Documents\grunt-ng-annotate>npm install
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files\\iojs\\\\node.exe" "C:\\Program Files\\iojs\\no
de_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! node v1.0.3
npm ERR! npm  v2.2.0

npm ERR! uid must be an unsigned int
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <http://github.com/npm/npm/issues>
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files\\iojs\\\\node.exe" "C:\\Program Files\\iojs\\no
de_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! node v1.0.3
npm ERR! npm  v2.2.0

The last block repeats multiple times.

It works fine when run from Git Bash, fails when run via cmd.

[rvagg]

@othiym23 got anything similar to this on record?

[bnoordhuis]

I think this should be filed as an npm issue, it calls fs.chown() or fs.fchown() with a bad uid.

[kenany]

@mzgol Is this present in npm@2.3.0 as well?

[rmg]

Ditto @kenany's question. npm@2.3.0 includes a commit that hopefully fixes a whole slew of these chown() problems.

[cjihrig]

I'm going to close this as an npm issue. If needed, we can always reopen.

[mgol]

@kenany Is there an easy way to update npm without using npm? Since npm -g install npm fails with the same error (and yes, I did try npm cache clean before).

EDIT: OK, it did work on the second run (and I could always do it via Git Bash).

[mgol]

It seems it's fixed in npm 2.3.0 so it should work fine in next io.js version by default. :)

[othiym23]

Sorry for going AWOL, everybody. It's been a very busy week for me. Yes, this is something that npm@2.3.0 addresses, so the next drop of npm to io.js will fix this.