I get constant errors in my JS files

[deiga]

message: "Process exited with code 1"
stack: "Error: Process exited with code 1
    at /Users/timosand/Dropbox/atom/packages/atom-lint/lib/linter/xml-base.coffee:14:29
    at ChildProcess.<anonymous> (/Users/timosand/Dropbox/atom/packages/atom-lint/lib/command-runner.coffee:99:7)
    at ChildProcess.EventEmitter.emit (events.js:104:17)
    at maybeClose (child_process.js:821:16)
    at Socket.<anonymous> (child_process.js:1038:11)
    at Socket.EventEmitter.emit (events.js:101:17) 
    at Pipe.close (net.js:459:12)"

[yujinakayama]

Could you try this with the latest atom-lint 0.14.1 which dumps detailed error information in Developer Console, and post the output here?

[lynnwallenstein]

I am getting a similar output. Using latest version 0.14.4 on Atom 0.120.0:

LinterError: Process exited with code 1
    command: ["scss-lint","--format","XML","/Users/lynnwallenstein/testingapp/rails/app/assets/stylesheets/structure/_layout.scss"]
    PATH: bin:/opt/boxen/homebrew/share/python:/opt/boxen/heroku/bin:/opt/boxen/foreman/bin:/opt/boxen/rbenv/shims:/opt/boxen/rbenv/bin:/opt/boxen/ruby-build/bin:/opt/boxen/phantomenv/shims:/opt/boxen/phantomenv/bin:node_modules/.bin:/opt/boxen/nodenv/shims:/opt/boxen/nodenv/bin:/opt/boxen/goenv/shims:/opt/boxen/goenv/bin:/opt/boxen/bin:/opt/boxen/homebrew/bin:/opt/boxen/homebrew/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/boxen/strap/bin
    exit code: 1
    stdout:
        <?xml version="1.0" encoding="utf-8"?><lint><file name="/Users/lynnwallenstein//testingapp/rails/app/assets/stylesheets/structure/_layout.scss"><issue linter="LeadingZero" line="12" column="15" length="20" severity="warning" reason="`.15` should be written with a leading zero as `0.15`" /><issue linter="Shorthand" line="23" column="12" length="11" severity="warning" reason="Shorthand form for property `padding` should be written more concisely as `20px 0` instead of `20px 0 20px`" /><issue linter="LeadingZero" line="25" column="15" length="18" severity="warning" reason="`.05` should be written with a leading zero as `0.05`" /><issue linter="LeadingZero" line="93" column="17" length="20" severity="warning" reason="`.15` should be written with a leading zero as `0.15`" /><issue linter="UnnecessaryParentReference" line="106" column="1" length="1" severity="warning" reason="Unnecessary parent selector (&amp;)" /><issue linter="IdWithExtraneousSelector" line="124" column="1" length="1" severity="warning" reason="Selector `#peek.disabled` can be simplified to `#peek`, since IDs should be uniquely identifying" /><issue linter="IdWithExtraneousSelector" line="137" column="1" length="1" severity="warning" reason="Selector `#dot-com-status.major` can be simplified to `#dot-com-status`, since IDs should be uniquely identifying" /><issue linter="IdWithExtraneousSelector" line="137" column="1" length="1" severity="warning" reason="Selector `#dot-com-status.minor` can be simplified to `#dot-com-status`, since IDs should be uniquely identifying" /><issue linter="IdWithExtraneousSelector" line="150" column="1" length="1" severity="warning" reason="Selector `#dot-com-status.major` can be simplified to `#dot-com-status`, since IDs should be uniquely identifying" /><issue linter="IdWithExtraneousSelector" line="150" column="1" length="1" severity="warning" reason="Selector `#dot-com-status.minor` can be simplified to `#dot-com-status`, since IDs should be uniquely identifying" /></file></lint>
    stderr:
         lint-view.coffee:57
LinterError: Process exited with code 1
  at /Users/lynnwallenstein/.atom/packages/atom-lint/lib/linter/xml-base.coffee:15:29
  at ChildProcess.<anonymous> (/Users/lynnwallenstein/.atom/packages/atom-lint/lib/command-runner.coffee:114:7)
  at ChildProcess.EventEmitter.emit (events.js:104:17)
  at maybeClose (child_process.js:821:16)
  at Socket.<anonymous> (child_process.js:1038:11)
  at Socket.EventEmitter.emit (events.js:101:17)
  at Pipe.close (net.js:459:12)

[yujinakayama]

@lynnwallenstein It seems that your issue is not same as @deiga's one. It's caused by a change of exit codes in SCSSLint 0.26. I just released atom-lint 0.14.5 which conform to the new exit codes.

[lynnwallenstein]

@yujinakayama Thanks will check it out. Sorry for hijaking the issue! Thought it was the same thing :\