Error pushing badgekit on Heroku (Self Hosting Guide)

[matteo...@gmail.com]

Hi all
I'm following Self Hosting Guide on Heroku.
I've succesfully installed API, but I' have problems with app opendbadges-badgekit.
When I run "git push heroku master" command I get back error you find below (I have put only few lines. Full message, 5000+ lines, is in attachment).
Any suggestion?
I'm using win7 but I think deploying on Heroku is indipendent from my system, is not it?
Thanks in advance for your help

Matt

 

C:\Heroku\bin\openbadges-badgekit>git push heroku master
Counting objects: 5218, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (2046/2046), done.
Writing objects: 100% (5218/5218), 5.34 MiB | 58.00 KiB/s, done.
Total 5218 (delta 3121), reused 5213 (delta 3118)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Node.js app detected
remote:
remote: -----> Reading application state
remote:        package.json...
remote:        build directory...
remote:        cache directory...
remote:        environment variables...
remote:
remote:        Node engine:         unspecified
remote:        Npm engine:          unspecified
remote:        Start mechanism:     Procfile
remote:        node_modules source: package.json
remote:        node_modules cached: false
remote:
remote:        NPM_CONFIG_PRODUCTION=true
remote:        NODE_MODULES_CACHE=true
remote:
remote: -----> Installing binaries
remote:        Resolving node version (latest stable) via semver.io...
remote:        Downloading and installing node 0.12.0...
remote:        Using default npm version: 2.5.1
remote:
remote: -----> Building dependencies
remote:        No cache available
remote:        Installing node modules
remote:
remote:        > node-proxy@0.6.0 install /tmp/build_6641fa4216aaf888cf793fa198173f84/node_modules/client-sessions/node_modules/node-proxy
remote:        > node-gyp configure build
remote:
remote:        child_process: customFds option is deprecated, use stdio instead.



remote:        make: Entering directory `/tmp/build_6641fa4216aaf888cf793fa198173f84/node_modules/client-sessions/node_modules/node-proxy/build'
remote:          CXX(target) Release/obj.target/nodeproxy/src/node-proxy.o
remote:        In file included from ../src/node-proxy.cc:33:0:
remote:        ../src/./node-proxy.h:108:36: error: ‘Arguments’ does not name a type
remote:           static Handle<Value> Clone(const Arguments& args);
remote:                                            ^
remote:        ../src/./node-proxy.h:108:47: error: ISO C++ forbids declaration of ‘args’ with no type [-fpermissive]
remote:           static Handle<Value> Clone(const Arguments& args);
remote:                                                       ^
remote:        ../src/./node-proxy.h:109:37: error: ‘Arguments’ does not name a type
remote:           static Handle<Value> Hidden(const Arguments& args);
remote:                                             ^
remote:        ../src/./node-proxy.h:109:48: error: ISO C++ forbids declaration of ‘args’ with no type [-fpermissive]
remote:           static Handle<Value> Hidden(const Arguments& args);
remote:                                                        ^
remote:        ../src/./node-proxy.h:110:37: error: ‘Arguments’ does not name a type
remote:           static Handle<Value> Create(const Arguments& args);
remote:                                             ^
remote:        ../src/./node-proxy.h:110:48: error: ISO C++ forbids declaration of ‘args’ with no type [-fpermissive]
remote:           static Handle<Value> Create(const Arguments& args);
remote:                                                        ^
remote:        ../src/./node-proxy.h:111:43: error: ‘Arguments’ does not name a
type
remote:           static Handle<Value> SetPrototype(const Arguments& args);
remote:                                                   ^
remote:        ../src/./node-proxy.h:111:54: error: ISO C++ forbids declaration
of ‘args’ with no type [-fpermissive]
remote:           static Handle<Value> SetPrototype(const Arguments& args);
remote:                                                              ^
remote:        ../src/./node-proxy.h:112:45: error: ‘Arguments’ does not name a
type


[...]



remote:                                         ^
remote:        make: *** [Release/obj.target/binding/binding.o] Error 1
remote:        make: Leaving directory `/tmp/build_6641fa4216aaf888cf793fa198173
f84/node_modules/node-sass/build'
remote:        gyp ERR! build error
remote:        gyp ERR! stack Error: `make` failed with exit code: 2
remote:        gyp ERR! stack     at ChildProcess.onExit (/tmp/build_6641fa4216a
af888cf793fa198173f84/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/li
b/build.js:267:23)
remote:        gyp ERR! stack     at ChildProcess.emit (events.js:110:17)
remote:        gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_
process.js:1067:12)
remote:        gyp ERR! System Linux 3.13.0-40-generic
remote:        gyp ERR! command "node" "/tmp/build_6641fa4216aaf888cf793fa198173
f84/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "re
build"
remote:        gyp ERR! cwd /tmp/build_6641fa4216aaf888cf793fa198173f84/node_mod
ules/node-sass
remote:        gyp ERR! node -v v0.12.0
remote:        gyp ERR! node-gyp -v v1.0.2
remote:        gyp ERR! not ok
remote:        Build failed
remote:        npm ERR! Linux 3.13.0-40-generic
remote:        npm ERR! argv "/tmp/build_6641fa4216aaf888cf793fa198173f84/.herok
u/node/bin/node" "/tmp/build_6641fa4216aaf888cf793fa198173f84/.heroku/node/bin/n
pm" "install" "--unsafe-perm" "--quiet" "--userconfig" "/tmp/build_6641fa4216aaf
888cf793fa198173f84/.npmrc"
remote:        npm ERR! node v0.12.0
remote:        npm ERR! npm  v2.5.1
remote:        npm ERR! code ELIFECYCLE
remote:
remote:        npm ERR! node-...@0.6.0 install: `node-gyp configure build`
remote:        npm ERR! Exit status 1
remote:        npm ERR!
remote:        npm ERR! Failed at the node-...@0.6.0 install script 'node-gyp
configure build'.
remote:        npm ERR! This is most likely a problem with the node-proxy packag
e,
remote:        npm ERR! not with npm itself.
remote:        npm ERR! Tell the author that this fails on your system:
remote:        npm ERR!     node-gyp configure build
remote:        npm ERR! You can get their info via:
remote:        npm ERR!     npm owner ls node-proxy
remote:        npm ERR! There is likely additional logging output above.
remote:
remote:        npm ERR! Please include the following file with any support reque
st:
remote:        npm ERR!     /tmp/build_6641fa4216aaf888cf793fa198173f84/npm-debu
g.log
remote:
remote: -----> Build failed
remote:
remote:        WARNING: Node version not specified in package.json
remote:        https://devcenter.heroku.com/articles/nodejs-support#specifying-a
-node-js-version
remote:
remote:        We're sorry this build is failing! If you can't find the issue in
 application code,
remote:        please submit a ticket so we can help: https://help.heroku.com/
remote:        You can also try reverting to our legacy Node.js buildpack:
remote:        heroku config:set BUILDPACK_URL=https://github.com/heroku/heroku-
buildpack-nodejs#v63
remote:
remote:        Love,
remote:        Heroku
remote:
remote:  !     Push rejected, failed to compile Node.js app
remote:
remote: Verifying deploy....
remote:
remote: !       Push rejected to secret-stream-7366.
remote:
To https://git.heroku.com/secret-stream-7366.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/secret-stream-7366.git'

 

[Nate Otto]

LIkely this line is the most important:

WARNING: Node version not specified in package.json

See https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version

I'm not sure what the right version of node to use is for BadgeKit. Perhaps you could try a couple specific versions, or perhaps dial it back from the default setting by a minor version or so.

The last time I was testing, I used v0.10.24. Does it work locally? What version of node are you using there?

`node -v`

Nate

[matteo...@gmail.com]

I'm using node 0.12.1 (the last I've have found on official site).

Locally it works with API and doesn't work with app. But I'm on Windows, so problems could be others....

 

I'll try to set version in package.json as you suggest. And if it will not work I'll try to downgrade node.

I'll update topic with result.

 

Thank you for you answer.

[matteo...@gmail.com]

Succesfully done!

It works with 0.10.24 in package.json.

Thank you very much

 

For imformation:

After build, I've got an app error because of my ACCES_LIST parameter. Setting right escape characters my app is started!

[\"\^mym...@maildomain.com\$\"]   ---wrong

[^mym...@maildomain.com$]   ---wrong

[\"^mym...@maildomain.com$\"]   ---right!

 

Thank you again

Matt

[Nate Otto]

Cool. Glad you figured out the ACCESS_LIST. That was tricky for a good number of people.

Nate

On Wednesday, April 8, 2015 at 3:58:29 AM UTC-7, matteo...@gmail.com wrote:

Succesfully done!

It works with 0.10.24 in package.json.

Thank you very much

 

For imformation:

After build, I've got an app error because of my ACCES_LIST parameter. Setting right escape characters my app is started!

[\"\^mym...@maildomain.com\$\"]   ---wrong

[^my...@maildomain.com$]   ---wrong

[\"^mym...@maildomain.com$\"]   ---right!

[Li Z.]

Thank you so much Matt! I had the same error and it took me so much time trying to figure it out until I saw your post. Changing node version to 0.10.25 worked! Thank you!!!

On Wednesday, April 8, 2015 at 6:58:29 AM UTC-4, matteo...@gmail.com wrote:

Succesfully done!

It works with 0.10.24 in package.json.

Thank you very much

 

For imformation:

After build, I've got an app error because of my ACCES_LIST parameter. Setting right escape characters my app is started!

[\"\^mym...@maildomain.com\$\"]   ---wrong

[^my...@maildomain.com$]   ---wrong

[\"^mym...@maildomain.com$\"]   ---right!

 

Thank you again

Matt