Alexander Emelin

https://github.com/centrifugal/centrifuge-python/releases/tag/0.4.0

Hello @ax-jochoa Thanks for the detailed report. Do you have a possibility to reproduce this on some of your devices locally? Ideally a goroutine dump could help here, but it...

Also adding some functionality to get debug/trace logs from `centrifuge-go` - please take a look at #106 , tried to add detailed logs to connect/reconnect phases. Again, if you can...

Hello @ax-jochoa Thanks for the update and super happy you were able to narrow down the case. Will try to dive deeper into your explanation, it seems I understand the...

Spent some time looking at current implementation. I do not see scenario where it may result into lost signal update TBH. The sync.Cond usage seems correct to me. Goroutines should...

For the example you provided yes – I see the problem, but in case of `centrifuge-go` we also have `for {` loop which I believe fixes the concern about the...

If the signal in `pushOrClose` is missed (no goroutine in Wait) – then `for` loop should help to eventually process the queued message. Even without `pushOrClose` the code should proceed...

@lahirumaramba hello, #695 does not contain any benchmarks and comparisons, did you make some local measurements or profiling maybe which demonstrated the difference? If yes - please share 🙏

Hello, I think it should be possible using [admin.external](https://centrifugal.dev/docs/server/admin_web#adminexternal) boolean option. Note – make sure to protect your admin UI from unauthorized access when exposing – extra firewall rules or...

Duplicate of https://github.com/gorilla/websocket/issues/886