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
From my user experience, situations like ECONNRESET, SQLITE_BUSY, etc. can all lead to disconnection that needs manual reconnect, and it is usually difficult to discover immediately. I think it is very necessary to add a 'keep-alive' mode. This mode should perform unlimited reconnection attempts after the connection is lost, just like what autobrr does.
The text was updated successfully, but these errors were encountered:
SQLITE_BUSY is not something that can happen as we synchronize our accesses and TL owns the db while it runs.
But that has nothing to do with reconnecting, it'll simply drop the message on the floor
Feature Description
From my user experience, situations like ECONNRESET, SQLITE_BUSY, etc. can all lead to disconnection that needs manual reconnect, and it is usually difficult to discover immediately. I think it is very necessary to add a 'keep-alive' mode. This mode should perform unlimited reconnection attempts after the connection is lost, just like what autobrr does.
The text was updated successfully, but these errors were encountered: