Moritz
Moritz
Gives me "image: unknown format"
Probably wont change after almost a year of your first Issue to that topic: @hirochachacha I would also really like to have anonymous support and when an interface is provided,...
Sure great idea. I just had this bug and need it fixed and in my experience fixing it and opening a PR is the fastest way. I did not read...
As suggested I moved the writeSent read/write into writeFrame. However I felt bad to fail silently if a double Close occurred, and is not really an net.ErrClosed since the connection...
Nice to hear that it makes things more predictable. :) @mafredri Yeah a test would be great. Sadly I am on a business trip until next monday, so until then...
So I had a moment to have look and wrote several approaches, but I have to admit that I find it kindof hard to test. I am not familiar enough...
Another note: your last commit makes my test (`go test -count=10 ./...`) gives me the "conn_test.go:623: failed to close WebSocket: failed to read frame header: EOF" again (sometimes). So the...
No I don't use CloseRead(ctx) in my application. I use the simple ```golang msgType, data, err := conn.Read(ctx) if websocket.CloseStatus(err) != -1 { ... } ``` or ```golang conn.Close(websocket.StatusInternalError, string(reason))...
Sure go ahead. My production go.mod is pinned to a commit, so no worries. ;)