Hi,
Here is what is going on. It try to rebuilding the sumary of block then it try to update headers but it keep failing.
so it undone the last block and start it rebuilding again and again
not sure why. any help would be great

Headers update requested
Headers update requested
Updated headers failed.
Updated headers failed.
Headers file requested
Receiving headers
Headers file received: 6A56B
LastBlock requested from block 60027
Sumary completed from 58924 to 60028

Block undone: 60028

nosolite version: v0.1
OS: ubuntu 20.04

Steps to reproduce:

• Create a new folder and cd into it: mkdir /tmp/nosolite && cd /tmp/nosolite
• Copy in the nosolite binary: cp ~/Downloads/nosolite .
• Create directory for wallet: mkdir wallet
• Create symlink from wallet to a path that doesnt exist: ln -s NOSODATA/doesntexist wallet/wallet.pkw
• Start nosolite: ./nosolite

Expected result:
Nosolite starts and displays an error to the user

Actual result:
Nosolite starts like normal, connects to mainnet, and displays the contents of the 0 address. Also note that the address field is blank.

In these two screen shots you can see the symlink to a path that doesn't exist, and what nosolite looks like

Checking Seed nodes IP in nl_data.pas, we can see current seed IP are:

0 47.87.132.148:X:X 45.83.151.30:8080:X:X 47.87.178.205;8080:X:X 47.87.174.224;8080:X:X 47.87.180.219;8080:X:X 47.87.137.96;8080:X:X 107.172.214.53;8080:X:X 198.23.134.105;8080:X:X 107.173.210.55:8080:X:X 107.172.21.121:8080:X:X 63.227.69.162:8080:X:X 20.199.50.27:8080:X:X

But, if we check on a seed node current IP are:

63.277.69.162
20.199.50.27
107.172.21.121
107.172.214.53
198.23.134.105
107.173.210.55
5.230.55.203
141.11.192.215
4.233.61.8

So, we need to remove old IP, add current Seed IP.

When my network is a bit congested, sometimes I get a state of the Nodes tab where all the entries are green but they contain no data from the nodes, not even the Error when it doesn't connect.

NosoLite v1.25
RaspberyOS 32b on a RaspberryPi 3B+

Problem:
Starting nosolite from the command line on macOS starts the app but does not allow the user to write in the app as the keyboard is "captured" in the command line. A workaround of placing the binary file in an macOS app folder also does not work because nosolite is designed to create files in the directory it is started from.

Possible solution:
Set file path for Darwin for have nosolite create the data and wallet folder in e.g., ${HOME}