[CLI and SSH] Linter plugin fails when a ~/.ssh/config exists about linter-jenkins HOT 9 CLOSED

I have seen something similar to this, because I was working on getting the linter working with automatic host authorization. What happens is those "INFO" messages from SSH are being returned as non-zero exit return values, so the underlying sb-exec backend npm treats them as failures. I tried circumventing this by allowing non-zero exit codes, but then errors become ignored, which becomes problematic for debugging.

This issue will likely be helpful when I revisit the related issue I saw. I was going to punt on it indefinitely, but it seems the problem arises in other situations and I can take a fresh look at it.

from linter-jenkins.

I doublechecked my notes and actually it is because SSH is outputting that "INFO" statement to stderr and not because of a non-zero return value. Sub that in for my comments above.

from linter-jenkins.

Workaround provided in fa76b3d. Please patch in the latest main.js to your local package at ~/.atom/packages, reload Atom, enable the new config option, and see if that fixes the issue for you. Make sure it works in both cases where the Jenkinsfile is valid and invalid.

from linter-jenkins.

I tried the new file, but no luck. I reloaded Atom twice just in case. Similar error appears:

/Users/guille/.atom/packages/linter/lib/linter-registry.js:159 [Linter] Error running Jenkins Error: Jan 21, 2019 8:19:45 PM org.apache.sshd.client.config.hosts.ConfigFileHostEntryResolver reloadHostConfigEntries
INFO: resolveEffectiveResolver([email protected]:2222) loaded 25 entries from /Users/guille/.ssh/config
    at ChildProcess.<anonymous> (/Users/guille/.atom/packages/linter-jenkins/node_modules/sb-exec/lib/index.js:41:20)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:925:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
(anonymous) @ /Users/guille/.atom/packages/linter/lib/linter-registry.js:159

Here's my ~/.ssh/config:

Host jenkins.dev.uts-squad.com
  hostname 192.168.10.8
  ProxyCommand ssh uts-bastion-dev -W %h:%p

Thank you for taking the time to try to solve this

from linter-jenkins.

I will put this back on the TODOs. Thanks for providing the config so I can attempt to duplicate this.

from linter-jenkins.

I just tested this and verified that Ignore stderr Output bypasses the issue with ssh outputting info and warning to stderr. Instead of the ssh message being thrown to the Atom error display, the linter diagnostic output is displayed as expected.

Sorry I cannot reproduce this when utilizing the fix I implemented for this.

from linter-jenkins.

I think I am seeing the same problem. I'm not getting any errors in atom, but I'm not getting any linter output either.

When I enable the debug output and I copy paste the command it is running I get the response I would expect, it is just not translating properly into atom.

I also tried the patch and new option that was discussed, but I saw no difference. Still no error messages.

I am also using a .ssh/config where I've set up a proxyCommand, so it seems like our use cases are very similar.

from linter-jenkins.

@mnordsletten You have a different situation since this issue is rooted in sb-exec treating all stderr file descriptor output as an error unless otherwise specified. Please open a new issue for your situation.

from linter-jenkins.

Closing due to unable to reproduce and lack of update. Please request a re-open if necessary.

from linter-jenkins.