Error: EEXIST, file already exists

[fivetwentysix]

file changed templates/application.hbs
EEXIST, file already exists '/Users/fivetwentysix/testapp/tmp/caching-writer-dest-dir_GE6biD.tmp'
Error: EEXIST, file already exists '/Users/fivetwentysix/testapp/tmp/caching-writer-dest-dir_GE6biD.tmp'
    at Error (native)
    at Object.fs.symlinkSync (fs.js:852:18)
    at symlink (/Users/fivetwentysix/testapp/node_modules/ember-cli/node_modules/symlink-or-copy/index.js:82:14)
    at Function.symlinkOrCopySync (/Users/fivetwentysix/testapp/node_modules/ember-cli/node_modules/symlink-or-copy/index.js:58:5)
    at /Users/fivetwentysix/testapp/node_modules/ember-cli/node_modules/broccoli-sourcemap-concat/node_modules/broccoli-caching-writer/index.js:103:21
    at lib$rsvp$$internal$$tryCatch (/Users/fivetwentysix/testapp/node_modules/ember-cli/node_modules/promise-map-series/node_modules/rsvp/dist/rsvp.js:489:16)
    at lib$rsvp$$internal$$invokeCallback (/Users/fivetwentysix/testapp/node_modules/ember-cli/node_modules/promise-map-series/node_modules/rsvp/dist/rsvp.js:501:17)
    at lib$rsvp$$internal$$publish (/Users/fivetwentysix/testapp/node_modules/ember-cli/node_modules/promise-map-series/node_modules/rsvp/dist/rsvp.js:472:11)
    at lib$rsvp$asap$$flush (/Users/fivetwentysix/testapp/node_modules/ember-cli/node_modules/promise-map-series/node_modules/rsvp/dist/rsvp.js:1290:9)
    at process._tickCallback (node.js:355:11)

Happens when I save any file with ember serve running.

This happens on a brand new project created with ember-cli-0.1.15

Here's a sample repo: https://github.com/fivetwentysix/ember-test-app

[Soliah]

This is happening to me too. Fresh app with 0.1.2-beta.1. Maybe something has changed in a dependency upstream?

https://gist.github.com/Soliah/edc8f012cc9e6800005d

[btecu]

Any of you using outputPaths?

#3365

[wstrinz]

I'm getting this too, tried with multiple versions of ember-cli. Not using outputPaths as far as I know, just a plain old ember new myapp.

[mariozig]

@fivetwentysix aside from stopping the server prior to making changes, have you found any sort of work around for this?

I'm experiencing it too in an unadulterated stock ember app on:

version: 0.2.0-beta.1
node: 0.12.0
npm: 2.1.8

@btecu no outputPaths here. Obviously it's referenced in node_modules/ember-cli/lib/broccoli/ember-app.js but the app i just tested on is a fresh install of ember cli, a newed up app, and no modifications other than rewriting a project file out.

[TimothyGu]

See also http://stackoverflow.com/questions/28846170/ember-cli-crash-on-rebuild-after-clean-install-what-am-i-doing-wrong

[btecu]

Probably a bad idea, but what I did to get around this problem was editing app/node_modules/ember-cli/node_modules/symlink-or-copy/copy-dereference/index.js and replace
fs.writeFileSync(dest, contents, { flag: 'wx', mode: srcStats.mode }) with
fs.writeFileSync(dest, contents, { flag: 'w', mode: srcStats.mode })

Restart ember server afterwards...

[bobbyhubbard]

Same issue here. See broccolijs/node-symlink-or-copy#4

[mariozig]

@bobbyhubbard are you sure it's the same bug? nodejs/node-v0.x-archive#8651 says it was fixed in node: 0.12.0 and i'm definitely seeing it with that version.

[stickbyatlas]

Hi folks - an hour ago, I did an npm update in my project directory. Immediately afterward, I started noticing the same crashing behaviour after changing a file while serving. Like others here, I suspect this has to do with an upstream dependency completely breaking everything, but I have no idea which one it could be. Would it be useful to share the contents of package.json here?

(For the record, the 'already existing' file is tmp/class-tmp_cache_dir-85EAruZ0.tmp , which is only relevant in that it's also a tmp/... file. The last step in the trace is Object.fs.symlinkSync. Would be happy to share the rest of the trace if it'll help.)

[fivetwentysix]

This is why npm needs something similar to gemfile.lock

[stickbyatlas]

If I knew how to reverse / undo npm update, I'd do it in a heartbeat. I can't even parse the output of the command, it's just a jumble of different dependency trees and conflict warnings. Every time I think "maybe Javascript has finally matured," something like this happens, the whole building topples, and I yearn for a classic, vetted language with a massive standard library.

[dopin]

I'm getting this too. I'm not sure if this works but if you specify "rimraf":"2.2.8" in package.json, it fixes.
rimraf 2.3.0 is just released about 7 hours ago from now.

[Soliah]

Confirming @dopin's suggestion of forcing rimraf to 2.2.8 works. Make sure to add this to dependencies and not devDependencies.

[JohnRodney]

@dopin's suggestion did not work for me. I tried cloning (broken), installing (broken), open old files (worked). Something new in the way that cache files are stored. If I just delete all the cache files with the commonatliy of "caching-writer-dest-dir{otherjunkhere}" then it saved ONCE fine. Next time back to broken.

[fotinakis]

Hitting this too just in the last few hours, yikes yikes...

[gevious]

thats the danger of being an early adopter ;)

[tehmaestro]

Yup, same here. I just updated Ember to 1.11 beta. If I go back to 1.10, will this go away?
EDIT: No it doesn't. Ignore the referenced issue.

EDIT2: It appears that there is an issue when the project is being watched. If I run ember build manually, every time, I don't get any errors.

[DenizOkcu]

@dopin 's fix works for me too.
Additional information:
npm install with rimraf v2.3.0:

npm WARN unmet dependency /home/{*}/node_modules/broccoli-caching-writer/node_modules/rimraf requires glob@'^4.4.1' but will load
npm WARN unmet dependency /home/{*}/node_modules/glob,
npm WARN unmet dependency which is version 4.0.5
npm WARN unmet dependency /home/{*}/node_modules/broccoli-es6modules/node_modules/broccoli-caching-writer/node_modules/rimraf requires glob@'^4.4.1' but will load
npm WARN unmet dependency /home/{*}/node_modules/glob,
npm WARN unmet dependency which is version 4.0.5
npm WARN unmet dependency /home/{*}/node_modules/broccoli-es6modules/node_modules/esperanto/node_modules/sander/node_modules/rimraf requires glob@'^4.4.1' but will load
npm WARN unmet dependency /home/{*}/node_modules/glob,
npm WARN unmet dependency which is version 4.0.5
npm WARN unmet dependency /home/{*}/node_modules/broccoli-sourcemap-concat/node_modules/broccoli-caching-writer/node_modules/rimraf requires glob@'^4.4.1' but will load
npm WARN unmet dependency /home/{*}/node_modules/glob,
npm WARN unmet dependency which is version 4.0.5

[olivierlesnicki]

Same here!

file changed controllers/journey.js
EEXIST, file already exists '/Users/pro/Workbench/Centrica/Github/home-move/tmp/class-tmp_cache_dir-fIzB9FpE.tmp'
Error: EEXIST, file already exists '/Users/pro/Workbench/Centrica/Github/home-move/tmp/class-tmp_cache_dir-fIzB9FpE.tmp'
    at Object.fs.symlinkSync (fs.js:741:18)
    at symlink (/Users/pro/Workbench/Centrica/Github/home-move/node_modules/ember-cli/node_modules/symlink-or-copy/index.js:82:14)
    at Function.symlinkOrCopySync [as sync] (/Users/pro/Workbench/Centrica/Github/home-move/node_modules/ember-cli/node_modules/symlink-or-copy/index.js:58:5)
    at /Users/pro/Workbench/Centrica/Github/home-move/node_modules/ember-cli/node_modules/broccoli-sourcemap-concat/node_modules/broccoli-caching-writer/index.js:103:21
    at lib$rsvp$$internal$$tryCatch (/Users/pro/Workbench/Centrica/Github/home-move/node_modules/ember-cli/node_modules/promise-map-series/node_modules/rsvp/dist/rsvp.js:489:16)
    at lib$rsvp$$internal$$invokeCallback (/Users/pro/Workbench/Centrica/Github/home-move/node_modules/ember-cli/node_modules/promise-map-series/node_modules/rsvp/dist/rsvp.js:501:17)
    at lib$rsvp$$internal$$publish (/Users/pro/Workbench/Centrica/Github/home-move/node_modules/ember-cli/node_modules/promise-map-series/node_modules/rsvp/dist/rsvp.js:472:11)
    at Object.lib$rsvp$asap$$flush [as _onImmediate] (/Users/pro/Workbench/Centrica/Github/home-move/node_modules/ember-cli/node_modules/promise-map-series/node_modules/rsvp/dist/rsvp.js:1290:9)
    at processImmediate [as _immediateCallback] (timers.js:345:15)

[olivierlesnicki]

I confirm that specifying "rimraf":"2.2.8" as a dependency fixed it.

[badazz91]

Hey guys,

I tried it with "rimraf":"2.3.0" - still getting the same issue.

I tried it with both ember-cli 0.1.15 and 0.2.0-beta.1.

version: 0.2.0-beta.1
node: 0.12.0
npm: 2.1.8

[olivierlesnicki]

@badazz91 Try rimraf 2.2.8 not 2.3.0

[jmurphyau]

@olivierlesnicki - Could you update your comment? It should be 'rimraf' but you've put 'rifraf'

[badazz91]

@olivierlesnicki ok using

`"rimraf":"2.2.8"`` as a dependency and a fresh npm install did the trick.

Also I noticed, that if you are using broccoli-sass and node 0.12.0 you need to make sure that you are using this version

"broccoli-sass": "^0.4.0" in your package.json

Thanks.

[stickbyatlas]

So, I totally don't even know what rimraf is, but this did the trick for me.
Thanks, all!

[BilalBudhani]

After adding "rimraf":"2.2.8" in my package.json everything started working. Thanks @dopin

[wautersj]

I confirm that the issue was resolved after adding "rimraf":"2.2.8" as a dependency and redoing npm

[ryanlabouve]

Yup. Thanks @dopin! Adding "rimraf":"2.2.8" as a dependency worked for me too.

[stefanpenner]

but also getting the ember-data warning. Thanks!

ya that's expected, we will support this until 0.3.x at which time we will stop supporting it, but we will make sure ember-data is updated accordingly.

[Danfitek]

I've tried upgrading to ember-cli 0.2.0 , Glob 4.4.2, and both versions of rimraf 2.2.8 and 2.3.1. I still get this error that the temp file exists.

[rwjblue]

@Danfitek - You should use glob@4.0.5 and rimraf@2.2.8, those are both specified by ember-cli in 0.2.0, but if you have added them manually to your project you will need to use these versions.

[lolmaus]

@Danfitek, ember-cli@0.2.0, glob@4.0.5 and rimraf@2.2.8. Also try removing glob and rimraf from your package.json.

[Danfitek]

@rwjblue and @lolmaus Thanks but I still can't get it working. I've tried specifying those versions of glob and rimraf in my package.json and also leaving them out of it. I've uninstalled them and reinstalled them. I'll keep trying.

[lolmaus]

@Danfitek, are you restarting your Ember CLI dev server?

[Danfitek]

Hi guys. I followed the full set of steps for upgrading ember-cli version (uninstall, clear caches, install, init...) https://github.com/ember-cli/ember-cli/releases and also restarted my machine. I also installed Watchman. It works perfectly now. It could have been any one of those steps. Thanks.

[iRonin]

If you encounter this issue with ember-cli-rails check Multiple (web server) workers cause multiple build servers and race conditions

[sulphur]

In my cas I was using ember-cli-coffeescript and after update the was app.js and router.js that were created. If you use ember-cli-coffeescript chek and delete app.js and router.js if you have the .coffee versions

[erichonkanen]

@sulphur I'm running into this issue and I think it has to do with ember-cli-coffeescript...

Error: EEXIST, file already exists '/Users/eric/Projects/myapp/overlord/build/client-web/tmp/coffee_script_filter-output_path-XZuGEV4i.tmp/client-web/routes/application.js'

myapp/routes/application.js does not exists only myapp/routes/application.coffee

any ideas?

[sulphur]

maybe try to remove your tmp dir etc.

[andrewhavens]

I also ran into this error while using ember-cli-coffeescript and trying to add ember-simple-auth. The solution was to convert my routes/application.coffee back to JavaScript. For some reason the default application route in ember-simple-auth conflicts with the one written in CoffeeScript.

[steady-daddy]

I encountered the same error when I put the file name in gulp.dest()

gulp.task('compass', function() {
    gulp.src(sassSources)
        .pipe(compass({
            ...
        })
        .pipe(gulp.dest( outputDir + 'css/style.css'))
        .pipe(connect.reload())
});

Removing style.css from gulp.dest( outputDir + 'css/style.css') fixed it for me. Not sure if rimraf has anything to do with this.