LiveKit Community

no, you don't have to. feel free to give it a go

bear in mind the user keeps the socket open the entire session

it's a case the server should handle.. helps me to track down the root cause

ok, pushed the client change as discussed

so if you see more panics, lmk and it'll be helpful to send the full log in an attachment. it'll help me read through what has lead to it.

attachment, i.e. file instead of raw message?

I think panics are more likely to happen with single node, given the reliance on the same channel

yeah, logs will be too much to paste in a msg without crowding out conversation

just drag a file over if it happens again

odd, in multi-node mode I am getting the hanging websocket connection again

so browser is stuck pending waiting for response from server

even though this was logged

```{"level":"info","ts":1611770565.228725,"caller":"service/rtcservice.go:108","msg":"new client connected","room":"RM_tsTxzJotGUhCHhppsRgPpk","roomName":"a62ac02a-54e4-4254-9667-989c40855d24","name":"WzEsICJwdWJsaWMiLCAidXNlciIsICIweEZGQzgwYmQyQTQxM2YzN0UxMjVEMzlDMjgxQ2M4NUI4OGRjZWJGMjAiXQ==","resSource":"0xc0012cb3e0"}```

interesting.. can you share the full log?

logs might be lost on that one but future logs I'll start retaining

I'm sure it'll happen again, and when it does I'll dump the full logs

i was able to add 38 tracks and the server as-is presented no problems

might be a function of load/timing with more participants but as of right now a 2 person call in multi-node mode is relatively stable