RATIONALE
In this issue #165 the user reports:
Actual behaviour
RPC timeout errors are printed, no sign that the client makes any peer connection.
The screen filled with only red error logs suggest to the user that shisui do not initialized correctly. It is not always the case.
Currently, if the node do not receive any help offer neither have its help offered to other nodes accepted, the logs looks like the decribed in the issue beforementioned althoug there is no bug.
The simple print of the message "Node added to bucket" whenever a new node is added to the bucket provide useful information: helps the user to differentiate a node that have no issues from a node that can not connect to the network and present real issues/bugs.
RATIONALE
In this issue #165 the user reports:
The screen filled with only red error logs suggest to the user that shisui do not initialized correctly. It is not always the case.
Currently, if the node do not receive any help offer neither have its help offered to other nodes accepted, the logs looks like the decribed in the issue beforementioned althoug there is no bug.
The simple print of the message "Node added to bucket" whenever a new node is added to the bucket provide useful information: helps the user to differentiate a node that have no issues from a node that can not connect to the network and present real issues/bugs.