BitShares Forum
Main => Technical Support => Topic started by: richiela on November 01, 2014, 10:44:58 pm
-
Just pulled from git and rebuilt; seems that wallet_get_balance is broken now.
>>> wallet_account_balance
10 assert_exception: Assert Exception
v.size() <= sizeof( fc::ripemd160 ) + 4: all addresses are less than 24 bytes
This has busted our workflow. Is there a new call we should be making?
-
Just pulled from git and rebuilt; seems that wallet_get_balance is broken now.
>>> wallet_account_balance
10 assert_exception: Assert Exception
v.size() <= sizeof( fc::ripemd160 ) + 4: all addresses are less than 24 bytes
This has busted our workflow. Is there a new call we should be making?
wow .. that most definitely IS a bug ..
maybe better not build from HEAD but your a release tag .. such as v0.4.23.1 or so ..
paging @toast @bytemaster
-
I've just re-created this issue when upgrading the client on ubuntu to v0.4.23.1-90-gbb33f21...
I noticed on upgrade, that one of the registered accounts that I use to send out pool payments 'x11-btsx-pool-minebitshares-com' is no longer listed when using 'wallet_list_my_accounts' or 'balance'.
wallet_account_balance x11-btsx-pool-minebitshares-com
results in...
'10 assert_exception: Assert Exception
v.size() <= sizeof( fc::ripemd160 ) + 4: all addresses are less than 24 bytes
{}
th_a address.cpp:43 is_valid
Happy to send the rest of the result of the error to a dev - not sure if the output contains sensitive data...
I've tried 'wallet_recover_accounts 10' but no-go, will keep troubleshooting...
-
I compiled the latest git head and had no issues .. seems to be a problem with your wallet ..
Can you import an older backup and recretae accounts and missing keys?
Could you pls also add an issue to the github repo?
-
Just pulled from git and rebuilt; seems that wallet_get_balance is broken now.
>>> wallet_account_balance
10 assert_exception: Assert Exception
v.size() <= sizeof( fc::ripemd160 ) + 4: all addresses are less than 24 bytes
This has busted our workflow. Is there a new call we should be making?
This was an issue that snuck into 0.4.23.1 due to a change that was intended for 0.4.24. It will be fixed in 0.4.24: https://github.com/BitShares/bitshares/issues/914