New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
View-only wallet creation leads to an avalanche of warnings and errors #6759
Comments
Those are fine, unless they're really many. Define many. |
Here's a dump of Monero wallet rpc outputs
|
I checked a couple txids in there, not found. Is this a monero fork ? Or testnet ? |
Ah yes, testnet. |
I checked a couple, and they do seem wonky. So all fine. That's a red herring AFAICT. |
Yes it's testnet. Ok I'll close the issue now, thanks for the info |
Well, the daemon should not become unresponsive. Those errors are unrelated, but this is still a bug. |
(so please get the data I asked for in my first comment if you can) |
Tested now, after the error |
Getting back to this error |
That sounds unlikely, so give actual repro steps. |
Steps are as follows:
|
Are you sure it's finished scanning ? |
I mean, open_wallet, get_balance or validate_address are wallet RPC. From your comments before the last one, you said daemon, which I had interpreted as the node, which was apparently incorrect. It now looks as if the wallet is just still busy syncing. |
Your explanation sounds reasonable, monero-wallet-rpc takes about 1 minute to sync. Is there a way to enqueue other RPC calls or detach the synchronisation to a separate thread? |
If you use open_wallet etc, you should be able to call auto_refresh on the wallet first, and set enable to false. Then you can refresh manually when convenient for you. |
After creating a view-only wallet with
generate_from_keys
I get a large amount of warnings and errors, mainly these three repeated several times. The RPC daemon becomes unresponsive to other calls.The text was updated successfully, but these errors were encountered: