search

edubkendo / atom-racer

Intelligent code completion for Rust in the Atom Editor. Requires Racer.
MIT License
115 stars 24 forks source link

"Racer returned a non-zero exit status" doesn't show racer failure message #48

Closed hawkw closed 8 years ago

hawkw commented 8 years ago

I keep getting "Racer returned a non-zero exit status: 1" messages. Obviously, the problem is my Racer install, not this plugin, but Racer works fine from the command line. Since this message doesn't display the message Racer failed with, it's difficult to figure out what's going on. Is there a way to get Racer failure messages out of the plugin?

armink commented 8 years ago

+1

areteCocoa commented 8 years ago

I too have run into this problem. I initially thought that my RUST_SRC_PATH was not configured, and it wasn't, but fixing that didn't stop the errors. I restarted Atom and that did not fix it either.

MatejLach commented 8 years ago

Can confirm this on my end as well.

yberreby commented 8 years ago

Same here, with the exit code being 101.

areteCocoa commented 8 years ago

Has anyone been able to replicate the issue/figure out what causes it? It seems to be random for me.

xooder commented 8 years ago

+1

archer884 commented 8 years ago

+1

xooder commented 8 years ago

Restart the Atom, it can be used

edubkendo commented 8 years ago

it's unfortunate but I'm not using either Rust or Atom anymore so it is difficult for me to find and fix these types of issues. I'd happily take a pull request though.

hawkw commented 8 years ago

Okay, I went and made a quick fork; it now caches the last message that went to stderr and adds that to the message in the alert when it receives a non-zero exit code.

If anybody wants to have a look at it, I'd appreciate a quick sanity check before I open a PR; I have basically no experience with CoffeeScript whatsoever.

edubkendo commented 8 years ago

@hawkw looks fine, except I had a question about if you meant return instead of preturn ?

hawkw commented 8 years ago

Yeah, that was a typo, I've since fixed it.

hawkw commented 8 years ago

Hopefully 3f5e66a387564d619356db364329569b7a2a4f43 will help some folks figure out what errors they're having.

edubkendo commented 8 years ago

yeah I'm not sure if there's anything left to do in this particular issue. Let's close it and if people encounter more specific errors they can open a new issue.