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

gaze update breaks things #416

Closed
yocontra opened this issue Apr 17, 2014 · 21 comments
Closed

gaze update breaks things #416

yocontra opened this issue Apr 17, 2014 · 21 comments

Comments

@yocontra
Copy link
Member

  • OSes not set up to build native modules (windows, osx stock, some linux)
  • process never exits

Post here if anything else was broken.

Temporary solution: npm install gaze@0.5.x -D

If it isn't fixed by tomorrow I'll roll it back in glob-watcher and wait until the new gaze is more stable.

Sorry all for the inconvenience, I should have had more tests to catch this.

@robatron
Copy link
Contributor

@contra , the temporary solution of npm install gaze@0.5.x -D isn't working as any of our shrinkwrap dependencies that depend on any recent version of gulp will depend on, and attempt to install, the latest version of Gaze.

Any chance you could revert your changes you made today to gulp and vinyl-fs since those changes appear to have introduced the issue?

This is a major issue for us. All builds and development are stopped until it's fixed :(

Thank you,
~The very sleepy devs of REI.com

@Voles
Copy link

Voles commented Apr 17, 2014

+1

@mweibel
Copy link

mweibel commented Apr 17, 2014

👍 not sure if I have the same problem though. On OSX everything runs fine for me with gulp 3.6.1 but on our build server (ubuntu) the process never exits. Is there a workaround which works? The gaze@0.5.x workaround doesn't seem to do it for me.

@Voles
Copy link

Voles commented Apr 17, 2014

The issue does occur on Mac as well (10.9.2) and the proposed workaround doesn't work either.

Full output on Mac:

> gaze@0.6.3 install /usr/local/lib/node_modules/gulp/node_modules/vinyl-fs/node_modules/glob-watcher/node_modules/gaze
> node-gyp rebuild

gyp: /Users/newfront/.node-gyp/0.10.26/common.gypi not found (cwd: /usr/local/lib/node_modules/gulp/node_modules/vinyl-fs/node_modules/glob-watcher/node_modules/gaze) while reading includes of binding.gyp
gyp ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:337:16)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:797:12)
gyp ERR! System Darwin 13.1.0
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/local/lib/node_modules/gulp/node_modules/vinyl-fs/node_modules/glob-watcher/node_modules/gaze
gyp ERR! node -v v0.10.26
gyp ERR! node-gyp -v v0.12.2
gyp ERR! not ok 
npm http 304 https://registry.npmjs.org/lodash.isobject
npm http 304 https://registry.npmjs.org/lodash._escapehtmlchar
npm http 304 https://registry.npmjs.org/lodash._reunescapedhtml
npm http 304 https://registry.npmjs.org/lodash._shimkeys
npm http 304 https://registry.npmjs.org/object-keys
npm http GET https://registry.npmjs.org/lodash._htmlescapes
npm http 304 https://registry.npmjs.org/core-util-is
npm http 304 https://registry.npmjs.org/string_decoder
npm http 304 https://registry.npmjs.org/isarray/0.0.1
npm ERR! gaze@0.6.3 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the gaze@0.6.3 install script.
npm ERR! This is most likely a problem with the gaze 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 gaze
npm ERR! There is likely additional logging output above.

npm ERR! System Darwin 13.1.0
npm ERR! command "node" "/usr/local/bin/npm" "install" "-g" "gulp@3.5.x"
npm ERR! cwd /usr/local/lib/node_modules
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.3
npm ERR! code ELIFECYCLE
npm http 304 https://registry.npmjs.org/lodash._htmlescapes
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /usr/local/lib/node_modules/npm-debug.log
npm ERR! not ok code 0

@imrefazekas
Copy link

The temporary solution of

npm install gaze@0.5.x -D

isn't working on Ubuntu, nor on my Mac.
The process.exit cannot be used due to the lots of parallel executions and highly structured build process.

@yocontra
Copy link
Member Author

Hmm I'll go ahead and roll back glob-watcher to gaze 0.5.x and publish that. An npm update should rectify the problem in about 30 minutes

@imrefazekas
Copy link

I replaced the gaze 0.5 directly in the folder

gulp / node_modules / vinyl-fs / node_modules / glob-watcher / node_modules

And works.

@yocontra
Copy link
Member Author

All done, go ahead and simply npm update. Once again sorry about this, I'll have to make sure I test on other OSes other than my own and Travis-CI's ubuntu with everything set up perfectly.

If anything is still not working let me know ASAP so I can get that solved before I go to sleep

@mweibel
Copy link

mweibel commented Apr 17, 2014

seems to work, thanks!

@alex6o
Copy link

alex6o commented Apr 17, 2014

thx! the fix works for me

@robatron
Copy link
Contributor

Fantastic, it's working now. Whew. Time for bed. Thanks!

@david-driscoll
Copy link

Awesome, thanks for the prompt fix!

@imrefazekas
Copy link

Works! Great! Thanks!

@yocontra
Copy link
Member Author

Forgot to cc @shama

@Voles
Copy link

Voles commented Apr 17, 2014

That was quick! Thanks, @contra!

@soulwire
Copy link

Thanks! That's fixed #414 also.

@thuld
Copy link

thuld commented Apr 17, 2014

Thanks!

@sc0ttwad3
Copy link

Confirmed working as well...and also #414.

@gaearon
Copy link

gaearon commented Jan 19, 2015

If anyone reading this still has this issue, double-check your tasks.
Maybe it's a Gulp task and not Gulp itself that is broken for you.

I spent a lot of time hunting this issue until I figured out it was happening due to gulp-shell needing a Node 0.11 fix.

@gmhenderson
Copy link

Thank you @gaearon for the followup, I was running into the same issue.

@crispen-smith
Copy link

Not sure if this is related, but I seem to be having issues with sass.watch

This is taken from my console:

Crispens-MacBook-Pro:site crispensmith$ sudo gulp sass
Password:
[23:09:26] Using gulpfile ~/Documents/goal/site/gulpFile.js
[23:09:26] Starting 'sass'...
[23:09:27] Finished 'sass' after 807 ms
Crispens-MacBook-Pro:site crispensmith$ sudo gulp watch
[23:12:06] Using gulpfile ~/Documents/goal/site/gulpFile.js
[23:12:06] Starting 'sass'...
[23:12:07] Finished 'sass' after 867 ms
[23:12:07] Starting 'watch'...
^C^C^C

in order to kill that process I seem to need to close the console window. If I run browser-sync it also seems to be failing on me.

What confuses me is that this seemed to be working less than 24 hours ago and I don't recall updating any dependancies in the interim.

Here's my gulpfile (it's pretty simple)

/*jslint node:true */
"use strict";

var gulp = require("gulp"),
sass = require("gulp-sass"),
browserSync = require("browser-sync"),
nodemon = require("gulp-nodemon");

gulp.task("test", function () {
console.log("TEST PASSED");
});

gulp.task("start", function () {
nodemon({
script: "node_modules/.bin/lcm",
args: ["server"],
nodeArgs: [],
ext: "js html",
env: {"NODE_ENV" : "development" }
});
});

gulp.task("sass", function () {
return gulp.src('../offsite/sass/*/.scss')
.pipe(sass())
.pipe(gulp.dest("resources/stylesheets"))
.pipe(browserSync.stream());
});

gulp.task("browserSync", function () {
browserSync.init({
proxy: "http://localhost:3000/wireframe/resequenced/second"
});
});

gulp.task("watch", ["sass"], function () {
gulp.watch('//*.css', ['sass']);
// gulp.watch('/
/.html').on("change", browserSync.reload);
// gulp.watch('/__/
.ejs').on("change", browserSync.reload);
// gulp.watch('/*/.js').on("change", browserSync.reload);
});

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