V12 Testing Thread

AjM said:
At least this: https://github.com/dashpay/dash/commit/8ba0328b71471ee7fe106a8477a8fa87f16c3e9e
and this: https://github.com/dashpay/dash/commit/ead842d6231599e3b9c3e7895a92770244c36d6c

Edit: and maybe this udjins fix also: https://github.com/dashpay/dash/commit/189e48328db11b691e4de24397ed9a6a5805028f
Click to expand...
Cool.. Thanks.

But I wish crowning or UdjinM6 would explain more... Was it because of something in Bitcoin10 code or something in Windows that was causing the problem?
 
moli said:
Cool.. Thanks.

But I wish crowning or UdjinM6 would explain more... Was it because of something in Bitcoin10 code or something in Windows that was causing the problem?
Click to expand...
I think it was restarting was faulty, and shutdown was not done properly.
But crowning and udjin will explain this i am sure.
 
AjM moli
This also https://github.com/dashpay/dash/commit/a33c569a1d0879b8d3869cb1f01e93f75216b75f helped though I still have no idea how could it crash there tbh but it did :confused:

Speaking of an overview of shutdown/restart crash(es) - it was not a single crash but rather a combination of many afaik and they were triggered by our code changes (basically we have more intensive work for wallet in background so we should have some additional safety checks) though some of them are related to bitcoin code imo. For example there is still smth that raise "LockedPage blablabla" error and we need to fix that. That's why we also have https://github.com/dashpay/dash/commit/ead842d6231599e3b9c3e7895a92770244c36d6c imported by crowning from latest bitcoin code - to make it appear in more meaningful message.
 
coingun said:
I leave the thread for a few hours and you guys make all this progress! Great job you guys/girls. Don't forget to go outside for a walk or something the sun will not hurt you, so I'm told.
Click to expand...

Actually the sun DOES hurt me, in my neck of the woods there's > 35° Celsius for about a week now :rolleyes:

I prefer to stay inside my air-conditioned home-office right now :smile:
 
The "mnbudget" voting has serious problem with the votes disappearing after a while... And the "mnbudget projection" list also comes and goes..
 
Hm... This is weird... "mnbudget show" would list the votes on the proposals differently on each wallet? And "mnbudget projection" would show the list on one wallet but not on another wallet.
 
Current mnbudget projection:
23:05:00

{
"Beer4flare" : {
"URL" : "http://www.dashpay.io/one.json",
"Hash" : "7fb0f2b251f42a6ecf6553a2261d9a5b0f32f5b7bae1570d52d4cabc28d2fe61",
"BlockStart" : 78500,
"BlockEnd" : 83525,
"TotalPaymentCount" : 100,
"RemainingPaymentCount" : 100,
"PaymentAddress" : "y9GHLgCNdZCLYb7yHc6dkahggjk65qhERV",
"Ratio" : 1.00000000,
"Yeas" : 68,
"Nays" : 0,
"Abstains" : 0,
"Alloted" : 15000000000,
"TotalBudgetAlloted" : 15000000000
},
"proposal-qwizzie1" : {
"URL" : "http://www.dashpay.io/one.json",
"Hash" : "bb57a8bb8069ad7292a78d9ad4de2bbe5795c452f1fdacacb916d58895202ca3",
"BlockStart" : 74000,
"BlockEnd" : 79025,
"TotalPaymentCount" : 100,
"RemainingPaymentCount" : 10,
"PaymentAddress" : "y5WWMBMxHsL5xmscwAyxUf2vfwMX58pprA",
"Ratio" : 1.00000000,
"Yeas" : 65,
"Nays" : 0,
"Abstains" : 0,
"Alloted" : 300000000000,
"TotalBudgetAlloted" : 315000000000
}
}
Click to expand...
 
Oh yah!
v0.12.0.9-8d7cce0

upload_2015-7-4_23-48-27.png


(Open dash.conf, type: windowtitle=yourwallettitle)
 
would also be nice if we could adjust the window size through dash.conf (set it to 480x332 for example), this would help when we are running multiple wallets
 
Last edited by a moderator:
Ok so now having different budgeting proposals how should I vote to a specific one?
 
splawik21 said:
Ok so now having different budgeting proposals how should I vote to a specific one?
Click to expand...

see post : https://dashtalk.org/threads/v12-testing-thread.5484/page-38#post-58278 and just adjust the command so it points to the proposal you want to vote on.
you should get all details of the proposal in question from mnbudget show

take a look at the first one on mnbudget show :

"proposal-qwizzie400" : {
"URL" : "http://www.dashpay.io/one400.json",
"Hash" : "00083e7191f01240389371284f946723ab3fe9e42743da629b26a311bdb91843",
"BlockStart" : 74000,
"BlockEnd" : 79025,
"TotalPaymentCount" : 100,
"RemainingPaymentCount" : 8,
"PaymentAddress" : "y5WWMBMxHsL5xmscwAyxUf2vfwMX58pprA",
"Ratio" : 0.00000000,
"Yeas" : 0,
"Nays" : 0,
"Abstains" : 0,
"Amount" : 340000000000

to vote you would use the black highlighted parts into the command which would make it :

dash-cli mnbudget vote proposal-qwizzie400 http://www.dashpay.io/one400.json 100 74000 y5WWMBMxHsL5xmscwAyxUf2vfwMX58pprA 3400 yes

This way even if you have multiple proposals with the same name, the one you specified with all these details gets your vote.

edit : a more simplistic vote command would be to just vote on the hashnumber by the way as that one is unique ..
 
Last edited by a moderator:
talking about stress testing the system with budget proposals, the mnbudget show command is actually getting slower to execute due to the many budget proposals now...

update : never mind, i did a bootstrap re-index and the mnbudget show is executed at normal speed now (it gives fast results)
 
Last edited by a moderator:
I still think mixing is not in normal state, too much collaterals.
But but there are also lots of old vers. masternodes at the same time in the testnet.
 
Well, I don't know, I just downloaded the latest from here: https://dashpay.atlassian.net/builds/browse/DASHL-DEV/latest/artifact/JOB1/gitian-linux-dash-dist/ Linux 64 bit, on a VPS, and it crashes. When I finally do dash-cli getinfo, I get "error: couldn't connect to server. I redownloaded and tried again 3 times. Each time, I gave myself permissions to execute files, yet the daemon doesn't completely start up (if I do getinfo early, I get "error: {"code":-28,"message":"Loading block index..."
 
You must log in or register to reply here.
Back
Top