Collaborate session was disconnected abnormally

[TENX-S]

Check for existing issues

• [X] Completed

Describe the bug / provide steps to reproduce it

https://user-images.githubusercontent.com/40336192/221329386-b2170fce-4d40-4d6d-b221-ab3b7d4b74f0.mov

Environment

My env: Zed: v0.74.2 (stable) OS: macOS 13.2.1 Memory: 8 GiB Architecture: aarch64

My colleague's: Zed: v0.74.2 (stable) OS: macOS 13.2.1 Memory: 8 GiB Architecture: x86_64

If applicable, add mockups / screenshots to help explain present your vision of the feature

No response

If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.

If you only need the most recent lines, you can run the zed: open log command palette action to see the last 1000.

My log:

2023-02-24T13:38:21 [INFO] open paths ["/Users/ares/Developer/Projects/rust-atomics-and-locks/RAL"]
2023-02-24T13:38:21 [INFO] set status on client 0: Authenticating
2023-02-24T13:38:21 [INFO] set status on client 0: Connecting
2023-02-24T13:38:21 [INFO] Opening main db
2023-02-24T13:38:21 [INFO] Opening main db
2023-02-24T13:38:21 [ERROR] No path stored for this editor
2023-02-24T13:38:22 [INFO] connected to rpc endpoint https://collab.zed.dev/rpc
2023-02-24T13:38:22 [INFO] unhandled notification experimental/serverStatus:
{
  "health": "ok",
  "quiescent": false,
  "message": null
}
2023-02-24T13:38:24 [INFO] add connection to peer
2023-02-24T13:38:24 [INFO] waiting for server hello
2023-02-24T13:38:24 [INFO] got server hello
2023-02-24T13:38:24 [INFO] set status to connected (connection id: ConnectionId { owner_id: 0, id: 0 }, peer id: PeerId { owner_id: 18, id: 256487 })
2023-02-24T13:38:24 [INFO] set status on client 0: Connected { peer_id: PeerId { owner_id: 18, id: 256487 }, connection_id: ConnectionId { owner_id: 0, id: 0 } }
2023-02-24T13:38:25 [INFO] unhandled notification experimental/serverStatus:
{
  "health": "ok",
  "quiescent": true,
  "message": null
}
2023-02-24T13:38:47 [INFO] leaving room
2023-02-24T13:38:47 [ERROR] share ended
2023-02-24T13:38:47 [ERROR] room creation failed: RPC request Call failed - failed to ring user
2023-02-24T13:38:47 [ERROR] error connecting to room
2023-02-24T13:38:47 [INFO] unhandled message RoomUpdated
2023-02-24T13:39:30 [ERROR] RPC request JoinRoom failed - room does not exist or was already joined
2023-02-24T13:39:50 [INFO] room is empty, leaving
2023-02-24T13:39:50 [INFO] leaving room
2023-02-24T13:39:51 [INFO] unhandled message RoomUpdated
2023-02-24T13:42:17 [INFO] room is empty, leaving
2023-02-24T13:42:17 [INFO] leaving room
2023-02-24T13:42:18 [INFO] unhandled message RoomUpdated
2023-02-24T13:52:58 [INFO] Opening main db
2023-02-24T13:54:52 [ERROR] no worktree found for diagnostics
2023-02-24T14:09:51 [ERROR] connection error: delay between messages too long
2023-02-24T14:09:51 [INFO] set status on client 0: ConnectionLost
2023-02-24T14:09:51 [INFO] set status on client 0: Reauthenticating
2023-02-24T14:09:51 [INFO] set status on client 0: Reconnecting
2023-02-24T14:09:53 [INFO] connected to rpc endpoint https://collab.zed.dev/rpc
2023-02-24T14:10:01 [INFO] add connection to peer
2023-02-24T14:10:01 [INFO] waiting for server hello
2023-02-24T14:10:01 [INFO] got server hello
2023-02-24T14:10:01 [INFO] set status to connected (connection id: ConnectionId { owner_id: 0, id: 1 }, peer id: PeerId { owner_id: 18, id: 256812 })
2023-02-24T14:10:01 [INFO] set status on client 0: Connected { peer_id: PeerId { owner_id: 18, id: 256812 }, connection_id: ConnectionId { owner_id: 0, id: 1 } }
2023-02-24T14:10:31 [ERROR] connection error: delay between messages too long
2023-02-24T14:10:31 [INFO] set status on client 0: ConnectionLost
2023-02-24T14:10:31 [INFO] set status on client 0: Reauthenticating
2023-02-24T14:10:31 [INFO] set status on client 0: Reconnecting
2023-02-24T14:10:34 [INFO] connected to rpc endpoint https://collab.zed.dev/rpc
2023-02-24T14:10:59 [INFO] add connection to peer
2023-02-24T14:10:59 [INFO] waiting for server hello
2023-02-24T14:10:59 [INFO] got server hello
2023-02-24T14:10:59 [INFO] set status to connected (connection id: ConnectionId { owner_id: 0, id: 2 }, peer id: PeerId { owner_id: 18, id: 256829 })
2023-02-24T14:10:59 [INFO] set status on client 0: Connected { peer_id: PeerId { owner_id: 18, id: 256829 }, connection_id: ConnectionId { owner_id: 0, id: 2 } }
2023-02-24T14:11:31 [ERROR] connection error: error reading rpc message from socket

Caused by:
    0: IO error: Connection reset by peer (os error 54)
    1: Connection reset by peer (os error 54)
2023-02-24T14:11:31 [INFO] set status on client 0: ConnectionLost
2023-02-24T14:11:31 [INFO] set status on client 0: Reauthenticating
2023-02-24T14:11:31 [INFO] set status on client 0: Reconnecting

My colleague's:

[TENX-S]

My colleague and I think it may be the websocket did not go through the proxy. Because we found this error message in the log:

2023-02-27T05:11:59 [ERROR] connection error: error reading rpc message from socket

Caused by:
    0: WebSocket protocol error: Connection reset without closing handshake
    1: Connection reset without closing handshake