there is something asynchronous and bad about monero's command interpreter

I'm going through the thing of typing "refresh" repeatedly.  Sometimes it gives the prompt back, as tho the command is complete, and then starts doing the thing of the command.  So it is asynchronous and bad.

The following is against a node on localhost.  And wtf is this "use the refresh command" at the end -- THAT IS WHAT I HAVE BEEN DOING REPEATEDLY.  If everything goes well, then soon I will never have to use this software again.

 

 / I locked your Monero wallet to protect you \
| while you were away                        |
\ see "help set" to configure/disable        /
 --------------------------------------------
        \   (__)
         \  (oo)\_______
            (__)\       )\/\
                ||----w |
                ||     ||


Locked due to inactivity. The wallet password is required to unlock the console.
Wallet password:
[wallet 44Evkv (out of sync)]: refresh
Starting refresh...
Error: refresh failed: no connection to daemon. Please make sure daemon is running.. Blocks received: 164835
[wallet 44Evkv (out of sync)]: refresh
Starting refresh...
Error: refresh failed: no connection to daemon. Please make sure daemon is running.. Blocks received: 82917
[wallet 44Evkv (out of sync)]: refresh
Starting refresh...
Error: refresh failed: no connection to daemon. Please make sure daemon is running.. Blocks received: 92907
[wallet 44Evkv (out of sync)]: refresh
Starting refresh...
Error: refresh failed: no connection to daemon. Please make sure daemon is running.. Blocks received: 96903
[wallet 44Evkv (out of sync)]: refresh
Starting refresh...
Error: refresh failed: no connection to daemon. Please make sure daemon is running.. Blocks received: 117882
Password needed (output received) - use the refresh command
Password needed (output received) - use the refresh command
Password needed (output received) - use the refresh command
[wallet 44Evkv (out of sync)]:

And there's also this, where it stops waiting for a password, when THERE IS NO PASSWORD ON THE WALLET.  (This is a local file encryption kind of password, so like the locking thing, is not needed if you secure it in the program's environment).

 

  ____________________________________________  
/ I locked your Monero wallet to protect you \
| while you were away                        |
\ see "help set" to configure/disable        /
 --------------------------------------------
        \   (__)
         \  (oo)\_______
            (__)\       )\/\
                ||----w |
                ||     ||


Locked due to inactivity. The wallet password is required to unlock the console.
Wallet password:
[wallet 44Evkv (out of sync)]: refresh
Starting refresh...
Enter password (output received):
Height 1337317, txid <bf60cbba1c321128b54237f7a5d290bb358998d95fe17a35c5eda96243a49b7b>, 490.000000000000, idx 0/0
Error: refresh failed: no connection to daemon. Please make sure daemon is running.. Blocks received: 50949
[wallet 44Evkv (out of sync)]: refresh
Starting refresh...
Error: refresh failed: no connection to daemon. Please make sure daemon is running.. Blocks received: 52947
[wallet 44Evkv (out of sync)]: refresh
Starting refresh...
Error: refresh failed: no connection to daemon. Please make sure daemon is running.. Blocks received: 42957
[wallet 44Evkv (out of sync)]: refresh
Starting refresh...
Error: refresh failed: no connection to daemon. Please make sure daemon is running.. Blocks received: 59940
[wallet 44Evkv (out of sync)]: refresh
Starting refresh...
Height 1574598 / 2845634


Comments

Post a Comment

Popular posts from this blog

the persistent idiocy of "privileged ports" on Unix

TCP and UDP have ports.  These are 16 bit; there are 65535 or so per IP address. These protocols don't care to differentiate between the ports.  Elsewhere, IANA presumes to operate a process to allocate "well-known" ports in the range 1-1023, "registered ports" in the range 1024-49151, and to reserve the remainder, 49152–65535, for "ephemeral" ports.  The caller end has to have a port, which is how replies get back within the virtual connection, and these are conventionally picked from the ephemeral range by the OS's networking stack. The whole idea of ports is ridiculous, because it allows ISPs to arse around presuming to decide which services they will "not allow".  Anything that allows IPSs to do anything other than shift opaque packets will allow ISPs to meddle and break things, and due to the Law of Meddling, if they can, they will.  I am currently working around an issue with Claro, a pretend ISP, blocking port 5060, allocated to SI
Read more

google is giving more and more 500 errors

Image
Total state capture and moral bankruptcy are not the only problems facing Google.  They are also giving an increasing rate of 500 Internal Server errors.  This is the sort that means they've messed up, but not in a way that they should have messed up.  On the other hand, they have drawn a lovely picture of a robot falling apart. Today's example is from Google Calendar under calendar.google.com.  I was trying to make an appointment, and now I'm doing this. I remember, in 2018, a friend trying to convince me that 500 Internal Server Errors no longer happened, or if they did it was my fault, and that they hadn't seen any for years, and some other things.  They assured me that they would love to see screenshots of such a rare specimen, which I bored them with for a while.  That friend happens to be a Google employee. Well, there are plenty of others posting about Google Calendar on twitter today, including screenshots of 500 Internal Server errors, so I doubt this one is en
Read more

Guernsey Waste in incorrect bag-rejection horror May 6th, 2024

Image
The rubbish collection folk at my new place seem pickier than at other places on Guernsey. Last week, they removed some card packaging that I'd included in the card and paper (plastic) clear bag, and left it on the lane.  This week, they have attached a rejection label entitled "Polite Notice".  Just like modern software-engineered error messages (see attached tag "extremely_general_error_handling"), this does not give a specific reason why the bag was rejected, but instead lists miscellaneous possible "reasons", leaving the victim guessing, or perhaps trying to follow a process of elimination. In this case, some possible reasons, which the label does not claim to be exhaustive ("was most likely because ..."), and of which none apply, are: (i) "did not have the required payment sticker" -- no, I applied to 90 litre sticker; or  (ii) (a) "too heavy" -- no, I estimate it was 3kg, and I easily supported the bag's weight o
Read more