Closed saadq closed 7 years ago
The plugin isn't able to talk with the rsense server. Can you check to see if it's running when this error occurs?
Admittedly, I know very little about the Ruby ecosystem. Do you mean to just run rsense start
and then open Atom? I tried doing that, but the errors still seem to happen.
The RSense server is a separate process. Try the following:
killall rsense
).rb
fileps aux | grep rsense
)Hmm, the errors are still there.
Although something kinda strange is happening.
If I manually run rsense start
, I'm not sure why the process isn't found when I try to kill it. Is it immediately stopping?
Looks like either rsense is crashing or never starting, have you looked at the logs at /tmp/rsense.log
?
Yup, there are some errors in there that I will need to fix, looks like a few missing gems for some reason.
Anyways, I'm guessing this isn't an issue with your package. Thanks for your help with debugging!
Hi, Anyone found the solution, I m also facing same. Please help
I'm facing the same issue. I've tried the steps above and nothing has helped.
As I type code in my editor, no autocompletion happens and errors like these show up in the console:
which rsense
gives the same path that is being used in the config forautocomplete-ruby
:/Users/squadri/.rvm/gems/ruby-2.4.1/bin/rsense
My Ruby version:
ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin16]
Let me know if I could provide any other details.