Closed somewhatnmc closed 4 years ago
@somewhatnmc Okay, so obviously we need to be catching those exceptions. That said, there's a potential secondary issue here, which is: is this Exception still happening for you when the blockchain is fully synced? (You can look at the Network dialog to see the chain height of the servers and of your client; if your client is the same height as the servers, then you're fully synced; otherwise you are not, and this Exception is expected.)
@somewhatnmc Also just to verify, did this show up with nc3.3.8
tag, or master branch, or some other revision? master branch is expected to take a while to sync, due to https://github.com/namecoin/electrum-nmc/issues/164
@JeremyRand this was using 3.3.8 binaries
Cannot reproduce issue currently, plausibly due to more Electrum-nmc servers being online. One, "Biolizard89" mentioned this may be the cause in "IRC".
Okay, thanks @somewhatnmc . I'll leave this issue open since the fact that the Exception is uncaught is clearly a bug that we need to fix, but it sounds like this bug isn't likely to surface much in typical use (except when there's trouble reaching a server).
Possible explanation for the Exception being raised: https://github.com/namecoin/electrum-nmc/issues/220#issuecomment-610128670 . If so then it should be fixed by 3.3.8.1.
Still leaving this issue open since catching the Exception is still important.
Consistent issue when checking name availability: