- Notifications
You must be signed in to change notification settings - Fork913
chore: migrate to coder/websocket 1.8.12#15898
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
mafredri left a comment• edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Should we updatecoder/tailscale
at the same time so that we don't run two versions of websocket?
I did some testing against bothcoder/tailscale
andcoder/coder
while working oncoder/websocket#476 and didn't notice any glaring issues so stamping this PR (even though it does not include said fix).
75de15b
toe029dbb
Compare
|
e029dbb
to814d296
Compare2c7f8ac
intomainUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Migrates us to
coder/websocket
v1.8.12 rather thannhooyr/websocket
on an older version.Works aroundcoder/websocket#504 by adding an explicit test for
xerrors.Is(err, io.EOF)
where we were previously gettingio.EOF
from the netConn.