Closed nmarley closed 2 years ago
Interesting. Just checked on my machine and it's working fine for me (same commit, different OS).
Very interesting. I'll try and git bisect it to find the commit where this started, but it will take a while because I have to recompile dependencies and everything from scratch each time because of linker issues. Maybe a functional test as @PastaPastaPasta suggested would help reduce the debug time.
Just out of curiosity, do you have the same issue if you try a new wallet file (createwallet
, then File
->Open Wallet
)? It would also be interesting to know if running keypoolrefill
would actually fix it, but then it couldn't be debugged further.
Running keypoolrefill
doesn't help with this specific wallet, but I haven't tried creating a new one. Will try that and see what happens. The wallet I am currently using was created on v0.17.0.3 I believe.
After running a git bisect to debug this, it looks like 254e12221779fcfb9ac35e7aa549b39ba788786d is the change which introduced this.
I created a patch on develop which reverts d25c0f21b and 254e12221 and this seems to work to fix the issue, which you can see at https://github.com/nmarley/dash/commit/df0cc17cd440507ccdcd2cc6232ce82c84867f2d.
I am assuming this is because the wallet is not an HD wallet but need to research a bit more. Will add some debug around here and see what comes up. I imagine that a bug was introduced with the different wallet flags.
Ok, I've created and funded 2 brand-new wallets from the branch above https://github.com/nmarley/dash/commit/df0cc17cd440507ccdcd2cc6232ce82c84867f2d, 1 of them is an HD wallet and the other is not.
I re-started DashCore at b0a8522d9d1a072f24810ca32b06b21e1b0fbc1c with each wallet loaded in turn, and the HD wallet had no issue but the regular wallet was giving the same error as the above. So it seems like the changes introduced some bug for regular non-HD wallets.
I will test this on Linux later just to verify it's not an OS thing, but I'm pretty sure I've got this nailed down to HD vs non-HD.
Thanks for finding the issue (and investigating its roots)! 👍 Pls test https://github.com/dashpay/dash/pull/4705
Thanks for the fix! That seems to work.
Describe the issue
I am not able to create any transaction it seems, after compiling and running dashd on the
develop
branch at commit b0a8522d9. My wallet is unlocked and has plenty of tDash.If I try and prepare a proposal collateral (gobject prepare) transaction, I get a message:
If I try and send to a fresh address in my own wallet, I get this message from the command line:
If I try and send via the GUI, I get these messages (please see attached images).
Can you reliably reproduce the issue?
If so, please list the steps to reproduce below:
Expected behaviour
It should send the Dash without the refillkeypool error.
Actual behaviour
An error is thrown about being unable to create a transaction and says to refillkeypool (doing this does not help, still gives the same error).
Machine specs:
Any extra information that might be useful in the debugging process.
Relevant debug.log entries after
gobject prepare
:Wallet has plenty of funds and not locked