Issue installing gcloud using command "npm install --save gcloud"

HI,

I have an issue installing gcloud package on my machine . I am getting following error. So could you please help me out with this.

F:\Projects\Kiran\Bald-Eagle\mcapi>npm install --save gcloud
npm WARN package.json [email protected] No README data

npm WARN package.json [email protected] No license field.

[email protected] install F:\Projects\Kiran\Bald-Eagle\mcapi\node_modules\gclou
d\node_modules\sse4_crc32
node-gyp rebuild

F:\Projects\Kiran\Bald-Eagle\mcapi\node_modules\gcloud\node_modules\sse4_crc32>i
f not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\np
else (node rebuild ) ..\node_modules\node-gyp\bin\node-gyp.js" rebuild )
configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYT
HON env variable.
gyp ERR! stack at failNoPython (C:\Program Files\nodejs\node_modules\npm\nod
e_modules\node-gyp\lib\configure.js:114:14)
gyp ERR! stack at C:\Program Files\nodejs\node_modules\npm\node_modules\node
-gyp\lib\configure.js:69:11
gyp ERR! stack at FSReqWrap.oncomplete (evalmachine.:95:15)
gyp ERR! System Windows_NT 6.3.9600
gyp ERR! command "node" "C:\Program Files\nodejs\node_modules\npm\node_modu
les\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd F:\Projects\Kiran\Bald-Eagle\mcapi\node_modules\gcloud\node_modules
\sse4_crc32
gyp ERR! node -v v0.12.7
gyp ERR! node-gyp -v v2.0.1
gyp ERR! not ok
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs
\node_modules\npm\bin\npm-cli.js" "install" "--save" "gcloud"
npm ERR! node v0.12.7
npm ERR! npm v2.11.3
npm ERR! code ELIFECYCLE

npm ERR! [email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the sse4_crc32 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls sse4_crc32
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! F:\Projects\Kiran\Bald-Eagle\mcapi\npm-debug.log

This is an issue with a dependency we use. Can you report this over on their repo? https://github.com/voxer/sse4_crc32

Thanks, and sorry you ran into this.

I don't think 4.0 had anything to do with this. The problem here is: "Can't find Python executable "python", you can set the PYTHON env variable." If https://github.com/Voxer/sse4_crc32/issues/39 turns up something else, and we need to update, we'll definitely do that.

No problem, we'll just wait to see what they say in https://github.com/Voxer/sse4_crc32/issues/39.

@stephenplusplus

@stephenplusplus This is far from the first time this library has caused a problem with installing gcloud. Are there really no alternatives that are more mature for doing CRC checks in Node? Or nothing else we can do to make this less of an issue ?

The thing that's unfortunate about this particular library is that it has native bindings-- that's only unfortunate because all of a sudden, developers get errors they have never seen before and it doesn't make sense why. All they did was install a JavaScript library. These errors will come up any time we use a library with native bindings.

What we can do is look for a software-only equivalent. I've tried in the past without success, but it's probably worth it to try again.

Doesn't CRC32 (regular) give shitty performance but no installation problems?

And then we can document the whole "If you want things to be super fast, just run npm install sse4_crc32 and we'll use that..." and then things will be faster.... ?

Working with the storage API is my first experience with crc32/c, but aren't crc32 and crc32c different algorithms that will give different results? The API gives us crc32c -- if crc32 works the same, then we can use something like this and be done with it. I doubt this type of performance tradeoff is anything the Node users will feel.

We'd need someone more knowledgeable to chime in, however I can say that certain people will definitely notice the difference (the Firebase folks for example definitely will be mad if we regress on performance going from C to JS), so we certainly need the ability to have "the faster way".

Having both would be pretty tricky since the problem happens at the point
of install. Maybe optionalDependencies can help us, I'll have to play with
it a bit to see how that would behave.

Worst case with only supporting the software for those who want hardware
would be that they would have to run the validation themselves. I (or
we) could make a small wrapper in a different module that makes it as easy
as possible.

On Saturday, August 22, 2015, JJ Geewax [email protected] wrote:

We'd need someone more knowledgeable to chime in, however I can say that
certain people will definitely notice the difference (the Firebase
folks for example definitely will be mad if we regress on performance going
from C to JS), so we certainly need the ability to have "the faster way".

—
Reply to this email directly or view it on GitHub
#817 (comment)
.

Wait... we can't set crc32 (software) as the dependency, and then in code:

try {
  crc = require('sse4_crc32');
} catch {
  crc = require('crc32');
}

?

And then anyone who wants "faster crc checks" can run npm install sse4_crc32 ?

Maybe! It's not a pattern I'm familiar with, I'll ask around if there's a
precedent here. If that is our best option, I'd try to modularize that out
and make a seamless API, otherwise our code would be quite gross.

On Saturday, August 22, 2015, JJ Geewax [email protected] wrote:

Wait... we can't set crc32 (software) as the dependency, and then in code:

try {
crc = require('sse4_crc32');
} catch {
crc = require('crc32');
}

?

And then anyone who wants "faster crc checks" can run npm install
sse4_crc32 ?

—
Reply to this email directly or view it on GitHub
#817 (comment)
.