You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use current connections to check if we are connected to sufficient peers. This is however incorrect since connections break (especially relay connections) and are only re-established when the next message is sent. In most cases, the connection will be re-established and everything will be fine.
Proposed solution
Instead of "current connections", use "recent connections" (1 min should be fine). So keep a timestamp of last seen connection and if that is more than 1min, then count the peer as "not connected".
The text was updated successfully, but these errors were encountered:
🐞 Bug Report
Description
We use current connections to check if we are connected to sufficient peers. This is however incorrect since connections break (especially relay connections) and are only re-established when the next message is sent. In most cases, the connection will be re-established and everything will be fine.
Proposed solution
Instead of "current connections", use "recent connections" (1 min should be fine). So keep a timestamp of last seen connection and if that is more than 1min, then count the peer as "not connected".
The text was updated successfully, but these errors were encountered: