Audit our implementation and trace disconnections and presence issues. Could be due to replica instances of pusher service.
When client A is in a stream, and client B joins, client A doesn't see client B as present. However, client B sees client A as present. And client A rejoining the stream by escaping and coming back resolves it. But overall it's unreliable and I don't know why.
Audit our implementation and trace disconnections and presence issues. Could be due to replica instances of pusher service.
When client A is in a stream, and client B joins, client A doesn't see client B as present. However, client B sees client A as present. And client A rejoining the stream by escaping and coming back resolves it. But overall it's unreliable and I don't know why.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Audit our implementation and trace disconnections and presence issues. Could be due to replica instances of pusher service.
When client A is in a stream, and client B joins, client A doesn't see client B as present. However, client B sees client A as present. And client A rejoining the stream by escaping and coming back resolves it. But overall it's unreliable and I don't know why.