Uncaught Error: spawn EACCES about linter-rubocop HOT 18 CLOSED

+1 on Atom 0.104.0

Uncaught Error: spawn ENOTDIR child_process.js:1017

from linter-rubocop.

Not sure how related this is, but if you've got rubocop in a non-system path (like, installed via RVM or rbenv), do you still get this error if you follow the suggestion on #7?

from linter-rubocop.

Yes that did correct my error... However I get another now

command and arguments ["/Users/philostler/.rvm/gems/ruby-2.1.2/bin/rubocop", "--format", "emacs", "/var/folders/qy/80j_mlk94yn5gz1k01z7sm380000gn/T/11465-966-xk02w4source.ruby"] linter.coffee:68
is node executable: false linter.coffee:91
stderr env: ruby_executable_hooks: No such file or directory

Tried different path combinations and different Rubies (Jruby, 1.9 & 2.1 through RVM, also the system Ruby), no joy, always the same error

from linter-rubocop.

I also get this I'm on rvm

from linter-rubocop.

The problem happened always on save file.

Atom Version: 1.0.3
System: elementary OS
Thrown From: linter-rubocop package, v0.3.1
Ruby: RVM (1.26.11)

Stack Trace

Uncaught Error: spawn EACCES

At /opt/atom/resources/app.asar/src/buffered-process.js:260

Error: spawn EACCES
  at exports._errnoException (util.js:734:11)
  at ChildProcess.spawn (child_process.js:1145:11)
  at Object.exports.spawn (child_process.js:977:9)
  at BufferedProcess.module.exports.BufferedProcess.spawn (/opt/atom/resources/app.asar/src/buffered-process.js:188:44)
  at new BufferedProcess (/opt/atom/resources/app.asar/src/buffered-process.js:52:14)
  at /home/ricardoleite/.atom/packages/linter-rubocop/index.coffee:27:9
  at /home/ricardoleite/.atom/packages/linter-haml/node_modules/fs-extra/node_modules/graceful-fs/graceful-fs.js:42:10
  at FSReqWrap.oncomplete (fs.js:77:15)

Commands

Config

{
  "core": {
    "disabledPackages": [
      "linter-erb",
      "atom-ctags",
      "autocomplete-elixir"
    ],
    "excludeVcsIgnoredPaths": false,
    "projectHome": "/home/ricardoleite/src"
  },
  "linter-rubocop": {
    "rubocopExecutablePath": "/home/ricardoleite/.rvm/gems/ruby-2.1.6/bin/rubocop",
    "executablePath": "/home/ricardoleite/.rvm/gems/ruby-2.1.6/bin/"
  }
}

Installed Packages

# User
Sublime-Style-Column-Selection, v1.3.0
atom-zeal, v0.1.3
atomatigit, v1.5.4
autocomplete-ctags, v0.3.1
autocomplete-haskell, v0.4.5
autocomplete-paths, v1.0.2
autocomplete-ruby, v0.1.0
color-picker, v2.0.11
css-snippets, v0.8.0
ctags-status, v1.3.3
docs-snippets, v0.8.0
file-icons, v1.6.3
git-log, v0.4.1
git-tab-status, v1.9.2
gulp-snippets, v0.6.1
haskell-ghc-mod, v0.8.8
html-id-class-snippets, v1.4.1
ide-haskell, v0.7.1
language-diff, v0.3.0
language-gitignore, v0.2.0
language-haskell, v1.3.0
language-txt2tags, v0.3.0
linter, v1.3.4
linter-coffeelint, v1.0.2
linter-haml, v1.0.0
linter-js-yaml, v1.1.1
linter-jshint, v1.1.5
linter-less, v2.0.3
linter-rubocop, v0.3.1
linter-ruby, v1.0.0
linter-tidy, v1.0.1
local-history, v3.2.3
merge-conflicts, vundefined
minimap, v4.12.2
minimap-bookmarks, v0.1.0
minimap-find-and-replace, v4.2.0
minimap-git-diff, v4.1.7
minimap-pigments, v0.1.3
minimap-selection, v4.3.0
pigments, v0.9.3
rspec-snippets, v0.4.0
ruby-block, v0.3.5
spotify-linux, v0.3.2
symbols-tree-view, v0.9.3
sync-settings, v0.6.0
tab-smart-sort, v0.1.4
wakatime, v4.0.12

# Dev
No dev packages

from linter-rubocop.

Just a sidenote: Node EACCESS error means that either the file you are accessing is inaccessible, if you are trying to execute it then it's not executable.

from linter-rubocop.

@steelbrain my rubocop path:

-rwxr-xr-x 1 ricardoleite ricardoleite 514 Jul  7 09:36 /home/ricardoleite/.rvm/gems/ruby-2.1.6/bin/rubocop

from linter-rubocop.

@ricsdeol Can you dump the value of command before this line and report what it is?
https://github.com/AtomLinter/linter-rubocop/blob/master/index.coffee#L27

from linter-rubocop.

I had to change my executable path to include rubocop in order for this to go away.

from

/Users/scashin133/.rvm/gems/ruby-2.2.2@global/bin

to

/Users/scashin133/.rvm/gems/ruby-2.2.2@global/bin/rubocop

from linter-rubocop.

@scashin133 - I also had to add /rubocop to the executable path, then the problem appears to have gone away.. Thanks for the work-around!

from linter-rubocop.

Going in to the rubocop linter settings and changing the path to include the actual rubocop file appears to have worked.

before: /usr/bin/
after: /usr/bin/rubocop

from linter-rubocop.

@scashin133 is right, that fixed it!

from linter-rubocop.

Can you dump the value of command before this line and report what it is?
https://github.com/AtomLinter/linter-rubocop/blob/master/index.coffee#L27

@steelbrain How I do this?

from linter-rubocop.

Sorry to bother but I'm still hitting the wall with this issue in atom 1.0.7, even with

  "linter-rubocop":
    ExecutablePath: "/Users/<user>/.rvm/gems/ruby-2.2.0/bin/rubocop"

Anyone else with the same problem?

from linter-rubocop.

@jossemarGT have you tried restarting atom? That fixed mine, also if you run /Users/<user>/.rvm/gems/ruby-2.2.0/bin/rubocop in your terminal does it start up rubocop?

from linter-rubocop.

+1

from linter-rubocop.

OMG I didn't see your mention @acrogenesis (kinda late to notice it), for future references it was my fault I didn't have rubocop into the project's gemset (installed by bundler).

from linter-rubocop.

Marking this as closed, the original reporter never responded, and this thread has gotten overly large with many different people's reports.

Generally this is caused by setting a directory in the Executable Path setting, instead of the full path to rubocop. If you have verified that you aren't doing this and are still having problems please file a new issue, thanks!

from linter-rubocop.