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
The plugin checks the node in the list nodes, that are the node of the network, we need to use the list peers, because are the peers connected to the node. However, with this information, we have some problems right now if we need to skip some nodes that is no present anymore in the command.
With this commit I'm fixing the collection data about info channel in case we have an error from the list nodes.
This is useful when the node have a channels with a node that is offline for a ling time and it is out of the gossip map.
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
With this commit I'm fixing the collection data about info channel in case we have an error from the list nodes.
This is useful when the node have a channels with a node that is offline for a ling time and it is out of the gossip map.
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
If we have an error during the on init phase, we do not storing the data. There is some error catch that we don't need to catch.
The text was updated successfully, but these errors were encountered: