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
Following up on #194, we should try to make LNDK a bit more resilient in the face of temporary, short-lived network errors, or LND restarts. Otherwise, if there's even just one short-lived error thrown, LNDK will just shut down. This means making sure to retry establishing a connection when subscribe_custom_messages or subscribe_peer_events return connection errors.
As @a-mpch mentioned, though, during this period it's possible we'll miss peer message events while we're waiting to reconnect, which can cause payment failures, etc. To get around the problem with missing peer events, we can call ListPeers to double-check if the OnionMessenger is totally synced up with LND.
The text was updated successfully, but these errors were encountered:
Description
Following up on #194, we should try to make LNDK a bit more resilient in the face of temporary, short-lived network errors, or LND restarts. Otherwise, if there's even just one short-lived error thrown, LNDK will just shut down. This means making sure to retry establishing a connection when
subscribe_custom_messages
orsubscribe_peer_events
return connection errors.As @a-mpch mentioned, though, during this period it's possible we'll miss peer message events while we're waiting to reconnect, which can cause payment failures, etc. To get around the problem with missing peer events, we can call ListPeers to double-check if the OnionMessenger is totally synced up with LND.
The text was updated successfully, but these errors were encountered: