Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

ST2 frozen by latest gosublime #45

Closed
zyxar opened this Issue · 10 comments

3 participants

@zyxar

The latest update (22/04) caused ST2 a start failure, falling into freeze here, on OS X 10.6, so that I have to remove gosublime so far. This issue occurred after I fired a gosublime upgrading. BTW, I have gocode installed.

@DisposaBoy
Owner

Only thing I can think of is that you don't have MarGo installed and the freeze is a side-effect of the automated installation. Try installing it manually go get github.com/DisposaBoy/MarGo

@chentmin

The latest MarGo code has an typo, line 123 of main.go, it listens on 127.9.5.1:57951. I changed the address to 127.0.0.1:57951 and MarGo can start successfully. But the GoSublime plugin still hangs, with MarGo started at the background.

@chentmin

The GoSublime.sublime-settings file, line 58, it attempts to connect to MarGo on 127.9.5.1:57951. Changing that to 127.0.0.1:57951 will fix the problem.

@zyxar

@chentmin thanks, the issue gone.
@DisposaBoy do I have to manually start MarGo?

@zyxar

@DisposaBoy I modified my GoSublime.sublime-settings file, solving the issue.

@DisposaBoy
Owner

I disabled the auto-install. I'll bring it back with auto-updating some other time. I'll leave this issue open as it's not actually fixed

@DisposaBoy
Owner

@zyxar It should start by itself as long as MarGo is in your $PATH or margo_cmd and margo_addr are set correctly in the config files.

@chentmin , that's not a typo. Is there an issue with MarGo listening on that address? it's a loopback address just like 127.0.0.1 is but if there is an issue I'll change it

@chentmin

@DisposaBoy Listening on 127.9.5.1 results in an error. I am using Go 1 on a Mac.

@zyxar

@DisposaBoy On OS X, MarGo would simply fail to start if binding to address 127.9.5.1:57951, with failure message "can't assign requested address"; while on Windows and Linux, it is okay.
Strictly, OS X only use 127.0.0.1/32 as loopback address by default.
According to RFC 3330:

127.0.0.0/8 - This block is assigned for use as the Internet host
loopback address. A datagram sent by a higher level protocol to an
address anywhere within this block should loop back inside the host.
This is ordinarily implemented using only 127.0.0.1/32 for loopback,
but no addresses within this block should ever appear on any network
anywhere [RFC1700, page 5].

May be Apple chose the 'original'.

@DisposaBoy
Owner

thanks I changed the default address

@DisposaBoy DisposaBoy closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.