Read context expiring closes websocket

[joaohaas]

ctx, _ := context.WithDeadline(mdm.ctx, time.Unix(0, 0))
_, _, err = ws.Read(ctx)  // failed to get reader: context deadline exceeded
_, _, err = ws.Read(context.Background())  // failed to get reader: WebSocket closed: read timed out: context deadline exceeded

From my understanding, the first context expiring is causing the websocket to close, which I believe is not correct. The same happens if you try to write after the first read, which is the use case I need (read until a timeout, and then send a message).

If this is the expected behaviour would be great to at least have it documented.

[joaohaas]

Probably is somehow related to this issue:
#289

[joaohaas]

Huh, just saw #242, should've checked closed tickets before.

Really unfortunate, I really like using contexts for stuff.

Closing this.

[nhooyr]

Yea sorry it's documented in the dev branch but that hasn't made it to master yet. #256