Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot push to Heroku #108

Closed
thomasorten opened this issue Mar 24, 2014 · 9 comments
Closed

Cannot push to Heroku #108

thomasorten opened this issue Mar 24, 2014 · 9 comments

Comments

@thomasorten
Copy link

Hi there!

I'm trying to push to Heroku, but I get a build error. Locally it works fine. I pulled from github, not yeoman. Any help would be appreciated!

First it fails here:

 > fsevents@0.1.6 install /tmp/build_a0071d31-3980-4c69-962d-3301a0ef1edb/node_modules/karma/node_modules/chokidar/node_modules/fsevents
       > node-gyp rebuild

       make: Entering directory `/tmp/build_a0071d31-3980-4c69-962d-3301a0ef1edb/node_modules/karma/node_modules/chokidar/node_modules/fsevents/build'
         CXX(target) Release/obj.target/fswatch/nodefsevents.o
       ../nodefsevents.cc:13:39: warning: CoreServices/CoreServices.h: No such file or directory
       ../nodefsevents.cc:19: error: 'FSEventStreamEventFlags' does not name a type
       ../nodefsevents.cc:20: error: 'FSEventStreamEventId' does not name a type
       ../nodefsevents.cc:128: error: 'ConstFSEventStreamRef' has not been declared
       ../nodefsevents.cc:128: error: ISO C++ forbids declaration of 'FSEventStreamEventFlags' with no type
       ../nodefsevents.cc:128: error: expected ',' or '...' before 'eventFlags'
       ../nodefsevents.cc:184: error: 'CFRunLoopRef' does not name a type
       ../nodefsevents.cc: In member function 'void node_fsevents::NodeFSEvents::Shutdown()':
       ../nodefsevents.cc:104: error: 'runLoop' was not declared in this scope
       ../nodefsevents.cc:104: error: 'CFRunLoopStop' was not declared in this scope
       ../nodefsevents.cc: In static member function 'static void* node_fsevents::NodeFSEvents::Run(void*)':
       ../nodefsevents.cc:113: error: 'CFStringRef' was not declared in this scope
       ../nodefsevents.cc:113: error: expected ';' before 'dir_names'
       ../nodefsevents.cc:114: error: 'dir_names' was not declared in this scope
       ../nodefsevents.cc:114: error: 'kCFStringEncodingUTF8' was not declared in this scope
       ../nodefsevents.cc:114: error: 'CFStringCreateWithCString' was not declared in this scope

Then details at the end:

4305 info linkStuff redis@0.7.3
4306 verbose linkBins redis@0.7.3
4307 verbose linkMans redis@0.7.3
4308 verbose rebuildBundles redis@0.7.3
4309 info install redis@0.7.3
4310 info postinstall redis@0.7.3
4311 info build /tmp/build_a0071d31-3980-4c69-962d-3301a0ef1edb/node_modules/karma/node_modules/chokidar
4312 info preinstall chokidar@0.8.1
4313 verbose linkStuff [ false,
4313 verbose linkStuff   false,
4313 verbose linkStuff   false,
4313 verbose linkStuff   '/tmp/build_a0071d31-3980-4c69-962d-3301a0ef1edb/node_modules/karma/node_modules' ]
4314 info linkStuff chokidar@0.8.1
4315 verbose linkBins chokidar@0.8.1
4316 verbose linkMans chokidar@0.8.1
4317 verbose rebuildBundles chokidar@0.8.1
4318 verbose rebuildBundles [ 'fsevents', 'recursive-readdir' ]
4319 verbose rebuild bundle /tmp/build_a0071d31-3980-4c69-962d-3301a0ef1edb/node_modules/karma/node_modules/chokidar/node_modules/fsevents
4320 info build /tmp/build_a0071d31-3980-4c69-962d-3301a0ef1edb/node_modules/karma/node_modules/chokidar/node_modules/fsevents
4321 info preinstall fsevents@0.1.6
4322 verbose linkStuff [ false,
4322 verbose linkStuff   false,
4322 verbose linkStuff   false,
4322 verbose linkStuff   '/tmp/build_a0071d31-3980-4c69-962d-3301a0ef1edb/node_modules/karma/node_modules/chokidar/node_modules' ]
4323 info linkStuff fsevents@0.1.6
4324 verbose linkBins fsevents@0.1.6
4325 verbose linkMans fsevents@0.1.6
4326 verbose rebuildBundles fsevents@0.1.6
4327 info install fsevents@0.1.6
4328 verbose unsafe-perm in lifecycle true
4329 info fsevents@0.1.6 Failed to exec install script
4330 error fsevents@0.1.6 install: `node-gyp rebuild`
4330 error Exit status 1
4331 error Failed at the fsevents@0.1.6 install script.
4331 error This is most likely a problem with the fsevents package,
4331 error not with npm itself.
4331 error Tell the author that this fails on your system:
4331 error     node-gyp rebuild
4331 error You can get their info via:
4331 error     npm owner ls fsevents
4331 error There is likely additional logging output above.
4332 error System Linux 3.8.11-ec2
4333 error command "/tmp/build_a0071d31-3980-4c69-962d-3301a0ef1edb/vendor/node/bin/node" "/tmp/build_a0071d31-3980-4c69-962d-3301a0ef1edb/vendor/node/bin/npm" "rebuild"
4334 error cwd /tmp/build_a0071d31-3980-4c69-962d-3301a0ef1edb
4335 error node -v v0.10.22
4336 error npm -v 1.3.14
4337 error code ELIFECYCLE
4338 verbose exit [ 1, true ]

 !     Push rejected, failed to compile Node.js app

To git@heroku.com:tabelltips.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'git@heroku.com:tabelltips.git'

@thomasorten
Copy link
Author

Btw, I had to change in my package.json "grunt-karma" to "0.8" and "karma" to "0.12.0", or else the build would fail, also locally.

@pilwon
Copy link
Owner

pilwon commented Mar 24, 2014

@thomasorten Try forcing git push git push heroku master -f

@yaru22
Copy link
Collaborator

yaru22 commented Mar 24, 2014

@thomasorten, which node version are you using? Is it v0.10.x or v0.11.x?

Also, in the latest repo, package.json should already have the latest grunt-karm and karma. You should do git pull.

@thomasorten
Copy link
Author

@yaru22 Locally, 0.10.22. I tried both .22 and .26 on Heroku. Did a pull, and reinstalled modules dir. Still no luck..

@pilwon Didn't work, unfortunately, same error.

@cevn
Copy link

cevn commented Apr 10, 2014

I'm having this same problem right now. Any resolutions?

@danielmahon
Copy link

bump

@pilwon
Copy link
Owner

pilwon commented May 8, 2014

I'm experiencing this error as well.

The problem is in the karma module is the problem. (related issues: linnovate/mean#411 and xolvio/rtd#113)

@pilwon pilwon closed this as completed in f5a83a9 May 8, 2014
@salam0smy
Copy link

i'm having the same problem?! any solutions?

@jelling
Copy link

jelling commented Aug 15, 2014

For anyone else having this problem you can temporarily work around it by removing karma. The commit referenced in the close put these files in a special Heroku file of things to ignore at runtime so that is the better solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants