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
It would be helpful if the ConnectionFSM class logged (even if TRACE or DEBUG level) when it attempts to make a connection, gives up on one, starts delaying, and then starts retrying. (I wanted this in order to verify the fix for MORAY-384, and I ended up using snoop to watch this instead. But in production that's not necessarily tenable, and it may well be useful to observe whether cueball is trying to establish connections.)
The text was updated successfully, but these errors were encountered:
It would be helpful if the ConnectionFSM class logged (even if TRACE or DEBUG level) when it attempts to make a connection, gives up on one, starts delaying, and then starts retrying. (I wanted this in order to verify the fix for MORAY-384, and I ended up using snoop to watch this instead. But in production that's not necessarily tenable, and it may well be useful to observe whether cueball is trying to establish connections.)
The text was updated successfully, but these errors were encountered: