Uncaught Error: ENOENT: no such file or directory, open 'C:\Users\<username>\Projects\my_project\tmp\web\elm\MyApp.elm' #61
Comments
|
Manually creating |
|
Yeah, it should create the directories automatically. Can you try the latest release? Your "source-directories" idea is in there, too. Thanks! |
|
So I saw! Just got to work, Atom has an update for linter-elm-make, installing, restarting, ./tmp was already cleared from last night, and testing, and: Error: ENOENT: no such file or directory, open 'C:\Users\<username>\Projects\my_server\tmp\web\elm\MessengerApp.elm'
at Error (native)
at Object.fs.openSync (fs.js:584:18)
at Object.module.(anonymous function) [as openSync] (ATOM_SHELL_ASAR.js:159:20)
at Object.fs.writeFileSync (fs.js:1234:33)
at Object.compileInWorkDirectory (C:/Users/<username>/.atom/packages/linter-elm-make/lib/linter-elm-make.js:584:8)
at Object.lint (C:/Users/<username>/.atom/packages/linter-elm-make/lib/linter-elm-make.js:396:25)
at promises.push.Promise.then._this.emitter.emit.linter (C:/Users/<username>/.atom/packages/linter/lib/linter-registry.js:63:26)
at C:/Users/<username>/.atom/packages/linter/lib/linter-registry.js:62:23
at Set.forEach (native)
at LinterRegistry.lint (C:/Users/<username>/.atom/packages/linter/lib/linter-registry.js:60:18)
at file:///C:/Users/<username>/.atom/packages/linter/lib/linter.coffee:98:16
at Function.module.exports.Emitter.simpleDispatch (C:\Users\<username>\AppData\Local\atom\app-1.8.0\resources\app.asar\node_modules\event-kit\lib\emitter.js:25:14)
at Emitter.module.exports.Emitter.emit (C:\Users\<username>\AppData\Local\atom\app-1.8.0\resources\app.asar\node_modules\event-kit\lib\emitter.js:125:28)
at C:/Users/<username>/.atom/packages/linter/lib/editor-linter.js:86:22
at file:///C:/Users/<username>/.atom/packages/linter/lib/helpers.coffee:25:18And the tmp directory is still entirely empty, it looks like it did not try copying the files over? |
|
Version of linter-elm-make is listed at 0.13.1. |
|
By "./tmp was already cleared", did you mean the entire directory was removed or just the files inside? If the tmp directory already exists, the linter will not copy the project files anymore, but will still watch the directory for changes. There's already 0.13.2 that shows notifications when linter is copying files to the work/temporary directory and when it's finished copying. It's safer to wait for the "Copied project files to work directory" message to appear first. Mind trying that out? Thanks! |
|
Ah currently our system at night has it that whenever we Checking for updates, found update for linter-elm-make, updating, complete, setting working directory back to r
elm-make.exe: elm-lang-html-66b1583: MoveFileEx "elm-lang-html-66b1583" "elm-lang\\html\\1.1.0": permission denied (Access is denied.)at line 1 col 1 in web\elm\MyApp2.elmWhere MyApp2.elm is the elm file I had open. |
|
Oh and no copy to tmp either |
|
Will leaving the |
|
I have been yep. :-) |
|
This happens for me either with a temporary directory or if I specify the folder... I think I will completely remove this package since it doesn't work as it should... I have also had troubles with it finding elm-make. I guess this package is not stable enough. |
|
Hi @positive07, can you check if these are relevant to your issue? #100, #101. Also, can you also try leaving the |
|
I left the directory black, I haven't tried entering on dev mode, I have already uninstalled the package. I tried using elm-make from the project, elm-make globally installed and elm-make installed with npm. Nothing helped, there was always one error, either it didn't find elm-make or it couldn't copy the files. I tried relatives. absolute and empty paths when setting the Also the issues posted here in GitHub seem to magically solve themselves and wheren't helpful at all, I would expect developers to help fixing this issues with this plugin but doesn't seem like it, everyone fixes the problem on their own and don't provide much feedback on how. About the plugins I have, I use elmjutsu and elm-format. I have laguage-elm autocompletion disabled. I have other not Elm related plugins like build. I wouldn't go through the hassle of removing all my plugins and installing them from zero just for the sake of debugging this. I have no experience with rebuilding plugins or modules whatever that is so I can follow the instructions you mentioned in #101 Windows 10 x64, Atom 1.13.0-beta6 ia32 |
|
Hi, I completely understand your frustration. Issues like this, though, are trickier to debug since they usually involve user configuration (and I don't have a Windows 10 machine which makes it trickier 😢). There are also Atom idiosyncrasies like that in #101. There's even an Elmjutsu issue before that was caused by another plugin modifying the default Atom behavior. There seems to be 2 issues: For (1), you didn't mention the Elm version, but I'm assuming it's 0.18? I honestly don't know yet why some folks (using Windows) are having issues after they upgraded to 0.18 :( For (2), you can try the following:
|
Work Directoryin the settings./tmp, enabledLint On The Fly, exited settings.Atom Version: 1.8.0
System: Microsoft Windows 10 Pro
Thrown From: linter-elm-make package, v0.12.2
Stack Trace
Uncaught Error: ENOENT: no such file or directory, open 'C:\Users\Projects\my_project\tmp\web\elm\MyApp.elm'
Commands
Config
{ "core": { "autoHideMenuBar": true, "disabledPackages": [ "autocomplete-go", "atom-powersnap", "activate-power-mode-delete", "autocomplete-dcd", "elm", "autocomplete-en-en", "spell-check", "latex-completions", "erlang-build" ], "projectHome": "C:\\Users\\<username>\\Projects", "themes": [ "atom-dark-ui", "solarized-dark-syntax" ] }, "linter-elm-make": { "alwaysCompileMain": true, "elmMakeExecutablePath": "C:\\Program Files (x86)\\Elm Platform\\0.17.1\\bin\\elm-make.exe", "lintOnTheFly": true, "workDirectory": "./tmp" } }Installed Packages
The text was updated successfully, but these errors were encountered: