search

johnwahba / go-tour

Automatically exported from code.google.com/p/go-tour
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

websocket connection closed #57

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Install go from homebrew
2. Install go-tour
3. type gotour in terminal
4. Look what happens

What is the expected output? What do you see instead?
I should see the working html page. Instead I see alert with followin text 
"websocket connection closed".

What version of the product are you using? On what operating system?
OSX 10.8.2
go 1.0.3

Please provide any additional information below.
I tried to open web page both in chrome and safari.

Inspect button in System Monitor show that:
/usr/local/Cellar/go/1.0.3/bin
/usr/local/Cellar/go/1.0.3/bin/gotour
/System/Library/CoreServices/Encodings/libCyrillicConverter.dylib
/usr/lib/dyld
/private/var/db/dyld/dyld_shared_cache_x86_64
/dev/ttys000
/dev/ttys000
/dev/ttys000
localhost:3999
localhost:59061->localhost:3999
->0xffffff8048b029c0
->0xffffff8041c312c0
count=0, state=0x2
localhost:3999->localhost:59061
localhost:3999->localhost:59120
localhost:3999->localhost:59121
localhost:3999->localhost:59122
localhost:3999->localhost:59123
localhost:3999->localhost:59124

Original issue reported on code.google.com by rainbu...@gmail.com on 13 Feb 2013 at 7:23

GoogleCodeExporter commented 9 years ago 
Which browser are you using?

Original comment by a...@golang.org on 13 Feb 2013 at 10:18

GoogleCodeExporter commented 9 years ago 
I tried to open web page both in chrome and safari. - It wrote that above.

Original comment by rainbu...@gmail.com on 14 Feb 2013 at 1:59

GoogleCodeExporter commented 9 years ago 
Sorry, I missed that part of the original report.

Are you passing any arguments to the gotour binary?

I have just submitted a couple of related changes to the gotour repository. 
Would you mind reinstalling with

go get -d code.google.com/p/go-tour/gotour

and trying again?

Thanks

Original comment by a...@golang.org on 15 Feb 2013 at 3:04

GoogleCodeExporter commented 9 years ago 
Same happens here with go 1.1

Original comment by ralphrma...@gmail.com on 15 May 2013 at 8:30

GoogleCodeExporter commented 9 years ago 
It also still happens after doing
go get -d code.google.com/p/go-tour/gotour

Original comment by ralphrma...@gmail.com on 15 May 2013 at 8:35

GoogleCodeExporter commented 9 years ago 
In my case I installed go with the Mac 64 pkg installer.

Original comment by ralphrma...@gmail.com on 15 May 2013 at 8:35

GoogleCodeExporter commented 9 years ago 
Still failing .. Has this issue been resolved

Original comment by coni...@gmail.com on 26 May 2013 at 5:23

GoogleCodeExporter commented 9 years ago 
No, the issue hasn't been resolved. I will investigate soon.

Original comment by a...@google.com on 26 May 2013 at 11:21

GoogleCodeExporter commented 9 years ago 
I have the same problem, installed via the package (ie. no brew).

Original comment by jonathan...@gmail.com on 28 May 2013 at 12:24

GoogleCodeExporter commented 9 years ago 
I solved this problem by installing homebrew, and re-installing go via 
homebrew, and then running the gotour built from:

go get code.google.com/p/go-tour/gotour

Original comment by jonathan...@gmail.com on 28 May 2013 at 12:54

GoogleCodeExporter commented 9 years ago 
I am investigating this now. It is very strange.

The only difference between a freshly built tour binary and the one bundled 
with go1.1, is that the latter sends this header line when the websocket 
connection is opened:

  Sec-WebSocket-Protocol: 

Yep, that's an empty protocol line. The fresh built binary does not send this 
line at all. I'm trying to figure out why this is different.

Original comment by a...@google.com on 28 May 2013 at 1:17

GoogleCodeExporter commented 9 years ago

Original comment by a...@golang.org on 28 May 2013 at 1:17

GoogleCodeExporter commented 9 years ago 
Aha, looks like it is this bug. I'll have to re-build the binary distributions 
to fix this issue.

 https://code.google.com/p/go/source/detail?r=78ad7f42aa2e546da67de466e9ae91f358478568&repo=net

Original comment by a...@golang.org on 28 May 2013 at 1:21

GoogleCodeExporter commented 9 years ago 
Go 1.1.1 is due to come out next week. The fixed version of the tour will be 
included. Marking as fixed. Please re-open if the problem persists after the 
1.1.1 release.

Original comment by a...@golang.org on 6 Jun 2013 at 12:01