Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Process exited with non-zero code 1

See original GitHub issue

Error: Process exited with non-zero code: 1
    at ChildProcess.<anonymous> (/home/xenith/git/dotfiles/.atom/packages/linter-flake8/node_modules/atom-linter/node_modules/sb-exec/lib/index.js:51:22)
    at emitTwo (events.js:100:13)
    at ChildProcess.emit (events.js:185:7)
    at maybeClose (internal/child_process.js:850:16)
    at Socket.<anonymous> (internal/child_process.js:323:11)
    at emitOne (events.js:90:13)
    at Socket.emit (events.js:182:7)
    at Pipe._onclose (net.js:477:12)

Atom: 1.10.0 Python: Python 3.5.2 :: Anaconda 4.1.1 (64-bit) (also happens with native python or python2) OS: Fedora 24

Issue Analytics

State:
Created 7 years ago
Comments:7 (1 by maintainers)

Top GitHub Comments

1reaction

xenithorbcommented, Sep 4, 2016

sigh

Strangely I noticed that even after disabling the package it still output the error message - you can see atom/packages/linter-flake8 in the error, so I know it’s coming from that package… however…

After I ~~disabled~~ uninstalled linter-flake8, now I also have the same message from linter-pep8:

Error: Process exited with non-zero code: 1
    at ChildProcess.<anonymous> (/home/xenith/git/dotfiles/.atom/packages/linter-pep8/node_modules/atom-linter/node_modules/sb-exec/lib/index.js:51:22)
    at emitTwo (events.js:100:13)
    at ChildProcess.emit (events.js:185:7)
    at maybeClose (internal/child_process.js:850:16)
    at Socket.<anonymous> (internal/child_process.js:323:11)
    at emitOne (events.js:90:13)
    at Socket.emit (events.js:182:7)
    at Pipe._onclose (net.js:477:12)

So I have no idea what’s going on

0reactions

Arcanemaguscommented, Sep 6, 2016

Looks like this was only getting reported here because Atom was loading the atom-linter library from this package. The bug in linter-pep8 has already been fixed in the latest release.