Uncaught Error: spawn ENOENT

[dengemann]

it seems something is causing trouble with the recent Atom verions.

cf. atom/atom#3091 (comment)

cc @kevinsawicki

I meanwhile switched to https://atom.io/packages/linter-python-pep8 and https://atom.io/packages/linter-python-pyflakes

[dmnd]

Hi @dengemann, can you help me reproduce this? I just tried with the following versions:

atom 0.119.0
linter 0.4.11
linter-pylint 0.1.2

Then I opened a Python file from the command line with atom pythonfile.py and things seemed to work. Can you be precise about exactly how this is failing?

[dengemann]

@dmnd I was basicaly getting errors like this one:

Failed to activate package named 'autocomplete-paths' Error: Could not resolve 'autocomplete-plus' to a package path
  at PackageManager.module.exports.PackageManager.loadPackage (/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:225:15)
  at PackageManager.module.exports.PackageManager.activatePackage (/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:108:21)
  at Object.module.exports.activate (/Users/dengemann/.atom/packages/autocomplete-paths/lib/autocomplete-paths.coffee:13:19)
  at Package.module.exports.Package.activateNow (/Applications/Atom.app/Contents/Resources/app/src/package.js:163:27)
  at /Applications/Atom.app/Contents/Resources/app/src/package.js:149:28
  at Package.module.exports.Package.measure (/Applications/Atom.app/Contents/Resources/app/src/package.js:95:15)
  at Package.module.exports.Package.activate (/Applications/Atom.app/Contents/Resources/app/src/package.js:143:14)
  at PackageManager.module.exports.PackageManager.activatePackage (/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:109:21)
  at PackageManager.module.exports.PackageManager.activatePackages (/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:98:14)
  at PackageManager.module.exports.PackageManager.activate (/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:85:19)
  at Atom.module.exports.Atom.startEditorWindow (/Applications/Atom.app/Contents/Resources/app/src/atom.js:367:21)
  at Object.<anonymous> (/Applications/Atom.app/Contents/Resources/app/src/window-bootstrap.js:14:8)
  at Object.<anonymous> (/Applications/Atom.app/Contents/Resources/app/src/window-bootstrap.js:20:4)
  at Module._compile (module.js:455:26)
  at Object.Module._extensions..js (module.js:473:10)
  at Module.load (/Applications/Atom.app/Contents/Resources/app/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:311:12)
  at Module.require (module.js:363:17)
  at require (module.js:379:17)
  at window.onload (file:///Applications/Atom.app/Contents/Resources/app/static/index.js:20:5)
 /Applications/Atom.app/Contents/Resources/app/src/package.js:168
activate linter-python-pep8 init.coffee:6
Window load time: 3279ms /Applications/Atom.app/Contents/Resources/app/src/window-bootstrap.js:18
Uncaught Error: spawn ENOENT events.js:82

with the same package versions you listed.

[dmnd]

That callstack looks unrelated to pylinter and instead related to autocomplete-paths. If you've got time, can you do the following steps to try to narrow down this issue:

1. Close any open tabs
2. Disable or uninstall the autocomplete-paths extension (which appears to be failing)
3. In settings, turn on "Lint Debug"
4. Open the devtools (cmd opt i)
5. Open a Python file

When you do the above steps, do you get any errors? Thanks for bearing with me while we work out what's wrong.

[dengemann]

@dmnd we already went through a debugging cycle, I did all that but the final spwan error remained. FYI also ran into these issue with the other liners I meanwhile used, especially after intense sessions with hundreds of open files and multiple directories.... It normally comes on saving.

[dmnd]

Thanks @dengemann I see there are actually a lot of these reports in lots of linters. I'll leave this open but it's probably going to be fixed in linter itself rather than linter-pylint.

Other possibly related bugs:

AtomLinter/linter-pycodestyle#4
steelbrain/linter#119
AtomLinter/linter-shellcheck#6
atom/atom#2055
atom/atom#2110

[dmnd]

I'm going to close this as I think sources of this that came from core linter have been fixed.

[dengemann]

Yes. I think so. Thanks.

2014-12-01 8:45 GMT+01:00 Desmond Brand [email protected]:

I'm going to close this as I think sources of this that came from core
linter have been fixed.

—
Reply to this email directly or view it on GitHub
#12 (comment)
.

[lazamar]

I had the same error. The reason was I didn't have pylint installed.
On ubuntu just sudo apt-get install pylint solves the problem.