Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

completion: Server Error solved by enabling File Sharing #58

Open
jonathonyule opened this issue Apr 17, 2016 · 4 comments
Open

completion: Server Error solved by enabling File Sharing #58

jonathonyule opened this issue Apr 17, 2016 · 4 comments

Comments

@jonathonyule
Copy link

Not sure how to file this but thought I would put it here if it helps someone else.

Was getting this error. #43 seemed to be related but flipping the excludeLowerPriority: false or true doesn't seem to affect this issue.

haxe / completion / server / starting `haxe` on `6112`
haxe / completion / server / Error: Couldn't wait on 127.0.0.1:6112

haxe / completion / server / process exit 1

I am running a very fresh install of El Capitan, atom, Haxe, luxe, etc. Turns out enabling File Sharing in system preferences allows atom to access the server and work as expected.

@jonathonyule
Copy link
Author

I may be wrong and am now still getting the error.

@jeremyfa
Copy link
Member

jeremyfa commented Apr 19, 2016

The error you have from the completion debug panel is "fine" if you have multiple atom windows opened. Basically, only one atom window can start the completion server at a single time. If some other windows are open, they will try (and fail) to start it because it is already running, which is fine. If you close the window that was running the server, it will then be restarted by another window.

So, you might get the error, which may be fine, but does the completion work or not? And if it doesn't, are you sure it doesn't come from your project? Do you have the issue on any project, and if not, does your project compiles properly?

I will update to latest atom to see if everything works fine still. (I am also on El Capitan)

@jonathonyule
Copy link
Author

It's hard to replicate the completion actually functioning. When it works it works really well. A project just opened in Atom the completion might work as expected, then other times it's the same error.

Restarting server or opening another window and starting that server still gives the same error.

I wish I could give more details.

@rippy
Copy link

rippy commented Jul 7, 2016

I was having the same error message, but a different root cause probably, here's how I fixed it.

Open up:
System Preferences -> Security & Privacy -> Firewall Options

Then, add the path to 'haxe' to your list of allowed applications. You have to give it the Cellar path and not the path to the symlink installed in /usr/local/bin by Homebrew if you're using that.

$ ll which haxe
lrwxr-xr-x 1 admin admin 29B Jul 7 09:38 /usr/local/bin/haxe@ -> ../Cellar/haxe/3.2.1/bin/haxe

screen shot 2016-07-07 at 10 04 17 am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants