-
Notifications
You must be signed in to change notification settings - Fork 875
bug: panic in coder ssh/vscodessh #15616
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Tailscale are also hitting it: golang/go#70528 Since they're raising it around the same time we're seeing it in the field, I'm suspicious it's related to a macOS update. The user who reported it is on macOS 15.1, which was released Oct 28th. |
@johnstcn are you able to reproduce this? |
@deansheather found an example Kernel packet that triggers the bug and confirmed that the upstream fix resolves for that packet. We got it from a customer who now say they can no longer reproduce even without a fixed binary. |
Thank you for pushing the upgrade already! I'm also seeing this, every time on coder ping and my IDE drops connection and reconnects every couple mins. I needed to upgrade to Sequoia earlier this week. Looking forward to the release including this fix! |
Thank you! I see the commit is from last week, so probably need to try a future release to include this? |
Correct, the next release will be v2.19.0. That should have the fix |
To bring in coder/tailscale#66 Closes #15616 (cherry picked from commit 2bba3d7)
--------------------- chore: migrate to coder/websocket 1.8.12 (#15898) Migrates us to `coder/websocket` v1.8.12 rather than `nhooyr/websocket` on an older version. Works around coder/websocket#504 by adding an explicit test for `xerrors.Is(err, io.EOF)` where we were previously getting `io.EOF` from the netConn.
Problem
Multiple users have reported the following stack trace when running
coder ssh
orcoder vscodessh
:What we know so far:
coder vscodessh
). Their log also shows the following line right before the panic (redacted):netmon_darwin.go
, implying that this is limited to the MacOS build of the CLI.The text was updated successfully, but these errors were encountered: