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
I wonder if simply setting a higher value here would work without issues. If not, we could perhaps allow a connection attempt to linger until the next attempt. These come at increasingly longer intervals
In either case, the next attempt cancels the previous, so if we were to make the first attempt to succeed, we'd have to increase the first number above.
ETA: If and when someone decides to tackle this, note that we have a little bit of UI showing the progress. Currently it tries to connect for 5 seconds, i.e. briefly, and then the notification will read something along “will try to connect in 30 seconds”. While this is far from ideal, we should think about how the notification should behave if we allow the connection attempt to be long. Things normally don't sit at “connecting...” for very long times
The default kexTimeout (5000ms) is too quick for me. It would be good to have a way to adjust it.
The text was updated successfully, but these errors were encountered: