Home → Problems →

Projects usings gulp fail to build

• Edit

yanickouellet555

17 Apr, 2015 02:58 PM

We have several projects using gulp to compile sass using gulp-sass (It's the only thing gulp do in these projects). Yesterday, everything worked fine, but today, every project using gulp is failling. The error message is

C:\Users\appveyor\AppData\Roaming\npm\node_modules\gulp\node_modules\liftoff\index.js:171
  throw err;
        ^
 Error: EPERM, ftruncate

Unable to cache a config file for v8flags to a your home directory
or a temporary folder. To fix this problem, please correct your
environment by setting HOME=/path/to/home or TEMP=/path/to/temp.
NOTE: the user running this must be able to access provided path.
If all else fails, please open an issue here:
http://github.com/tkellen/js-v8flags
Command exited with code 8

We try to set an environment variable HOME=C:\Users\appveyor\, but this is not solving our problem. I checked gulp and liftoff, the gulp dependency that is causing the problem and they were not updated recently, so the problem is probably not from theses libraries.

Have-you an idea of the source of the problem?

1. 1 Posted by jim on 17 Apr, 2015 04:15 PM

   

   We're having this same issue, it seems to be erroring out before it hits any of the actual gulp tasks.

   • Edit

2. Support Staff 2 Posted by Feodor Fitsner on 17 Apr, 2015 04:52 PM

   

   Can you guys provide some test public repository with minimum files just to reproduce this issue?

   • Edit

3. Support Staff 3 Posted by Feodor Fitsner on 17 Apr, 2015 05:04 PM

   

   https://github.com/tkellen/js-v8flags/issues/17

   • Edit

4. 4 Posted by jim on 17 Apr, 2015 05:14 PM

   

   https://bitbucket.org/j_i_m/appveyor-gulp-test

   Pre build cmd script:
   npm install -g gulp
   npm install
   gulp

   • Edit

5. 5 Posted by yanickouellet55... on 17 Apr, 2015 06:11 PM

   

   The problem is caused by the issue in js-v8flags that Feodor pointed out. Since I guess we will have to wait for js-v8flags to release a patched version, I found a temporary workaround. We can use npm shrinkwrap to lock dependencies. v8flags should be at version 2.0.2, which does not have the bug.

   However, since gulp is installed globally, it still use version 2.0.4. To fix that issue, I use node_modules/.bin/gulp instead of gulp to use the local version, which have the correct dependency. Doing so solve the problem.

   I know that it's not the best solution ever, but I think this should suffice until v8flags is patched.

   • Edit

6. 6 Posted by jim on 17 Apr, 2015 06:22 PM

   

   Thanks for the info, I'll probably leave it alone and hope for a fix by Monday. If not I'll definitely use your workaround. Cheers.

   • Edit

7. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:55 AM.