v0.11.2.x Testing

yidakee said:
eduffield crowning

My resolution setting are the same as my previous post - https://darkcointalk.org/threads/v0-11-2-x-testing.4202/page-9#post-47259
Main OS = OSx 10.9.5, Retina 2560 x 1600
VM resized -> odd numbers as I drag the window size
VM full-screen 1280x800 16:10
Click to expand...

I can not re-produce this with Ubuntu running in VirtualBox.

Before I install VMware (what I want to avoid): 1280x800 for full-screen is already not that much....could it be that the resized window is just too small for the wallet?

The minimum requirement for the wallet is 960x585. If your window is smaller some parts will be missing of course. If your resize it to something bigger the wallet should automatically adjust until it's fully visible.

Can you please check the window size?
 
I have 2 wallets (self-build Linux and official Win 32) stuck at block 25273.

Anyone else?


(deleting peers.dat and resync did NOT help)

Edit: I mined some blocks and now it's synced. Either everything's okay now or I'm forked :grin:
 
Last edited by a moderator:
crowning said:
I have 2 wallets (self-build Linux and official Win 32) stuck at block 25273.

Anyone else?


(deleting peers.dat and resync did NOT help)

Edit: I mined some blocks and now it's synced. Either everything's okay now or I'm forked :grin:
Click to expand...

Apparently all of the miners are on the old version, everybody --reindex and start mining!
 
******************** TESTNET : 11.2.13 - All Users *********************************

- Client version bump
- Many CSS fixes, alignment fixes and other styling changes - Crowning/Snogcel/Udjin
- Fixed race conditions for masternode payment selection
- Disabled history truncaction - Crowning
- Fix balance label UI issue - Udjin

** Compiling - if you get a 404 try again in a bit

Windows 32bit:
http://bamboo.darkcoin.qa/artifact/DRKW-DEV/JOB1/build-172/gitian-win-darkcoin-bin/32/dash-qt.exe

Mac OS X:
http://bamboo.darkcoin.qa/browse/DR...1/gitian-osx-dash-dist/dash-0.11.2.13-osx.dmg

Linux 32bit:
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-172/gitian-linux-dash-bin/bin/32/dash-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-172/gitian-linux-dash-bin/bin/32/dashd

Linux 64bit
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-172/gitian-linux-dash-bin/bin/64/dash-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-172/gitian-linux-dash-bin/bin/64/dashd
 
Last edited by a moderator:
eduffield said:
******************** TESTNET : 11.2.12 - All Users *********************************

Please --reindex, if you had a client that forked send the debug.log to [email protected]
Click to expand...

Unfortunately the --reindex truncated the logfiles of both my clients so the logfiles are useless now :sad:

BTW, on Github:
Code: 
#define CLIENT_VERSION_MAJOR  0
#define CLIENT_VERSION_MINOR  11
#define CLIENT_VERSION_REVISION  2
#define CLIENT_VERSION_BUILD  11
 
Last edited by a moderator:
Just throwing this out there...

Given that there still seems to be some bugs with the current version, wouldn't it be better just to re-release the 0.11.1.25 wallet with the new name DASH and the new css theme tomorrow -- and leave the coding fixes/improvements in 11.2.x for later?

I don't think we want a big clalamity and 4 or 5 fixes released on the day we officially rebrand.
 
Last edited by a moderator:
coingun said:
The PoS (Proof of Service) code performs quality of service checks on the masternodes. The way I understand it then increments or decrements a score based on the results of it's checks. Masternode's with a higher score are performing more optimally.

Edit: that description might be a bit overly simplified maybe someone else can chime in.
Click to expand...

Oh, can we see how our servers are performing, is anything written up on this yet? Thanks!
 
found pre-existing bug: coin control list selection date column does not sort rows.

affects versions v0.11.1.x and v0.11.2.x (and possibly others)

While I'm posting bugs: debug window history is broken too. To reproduce:
open debug console
type 'masternode count' -- get response
type 'getmininginfo' -- get response
hit up arrow twice. see 'masternode count', hit enter -- get response
hit up arrow to replay 'getmininginfo' -- not in history
 
Last edited by a moderator:
moocowmoo said:
...cut...
While I'm posting bugs: debug window history is broken too. To reproduce:
open debug console
type 'masternode count' -- get response
type 'getmininginfo' -- get response
hit up arrow twice. see 'masternode count', hit enter -- get response
hit up arrow to replay 'getmininginfo' -- not in history
Click to expand...
I'm not sure if that's a but, it never worked before. It might be a safety thing, so that passwords are not stored anywhere? Can anyone verify that? I've only gotten the last thing I entered for a while now.

I was wondering, the first time I started the masternode, my wallet asked me if I wanted to donate 5%, and I said yes. Then it warned that if I didn't want to see this question again, that I should put a note in my conf file. Thing is, I didn't touch my conf file, and I haven't been asked again. I never made a conf file in my testnet3 folder, because everything always seemed ignored (and seems to take info from my conf file under \AppData\Dash.

So am I messing up my testnet setup? Should I make a Dash.conf in testnet3 and also, why don't I get asked if I want to donate again? (we should be bugging people ;) )
 
Tante, I think this is a better answer to your original question about PoSe scores:
https://dashtalk.org/threads/v0-11-2-x-testing.4202/page-19#post-48276

TanteStefana said:
Oh, can we see how our servers are performing, is anything written up on this yet? Thanks!
Click to expand...
I believe Evan is already working on it, the code is probably here:
https://github.com/darkcoin/darkcoin/commit/bb7672fb0f6d5d57475b250f633bd2cebe6c3e10?diff=split

Evan's comments on the code:
+ Masternode - Proof of Service
+
+ -- What it checks
+
+ 1.) Making sure Masternodes have their ports open
+ 2.) Are responding to requests made by the network
+
+ -- How it works
+
+ When a block comes in, DoMasternodePOS is executed if the client is a
+ masternode. Using the deterministic ranking algorithm up to 1% of the masternode
+ network is checked each block.
+
+ A port is opened from Masternode A to Masternode B, if successful then nothing happens.
+ If there is an error, a CMasternodeScanningError object is propagated with an error code.
+ Errors are applied to the Masternodes and a score is incremented within the masternode object,
+ after a threshold is met, the masternode goes into an error state. Each cycle the score is
+ decreased, so if the masternode comes back online it will return to the list.
+
+ Masternodes in a error state do not receive payment.
+
+ -- Future expansion
+
+ We want to be able to prove the nodes have many qualities such as a specific CPU speed, bandwidth,
+ and dedicated storage. E.g. We could require a full node be a computer running 2GHz with 10GB of space.
Click to expand...
 
TanteStefana said:
I'm not sure if that's a but, it never worked before. It might be a safety thing, so that passwords are not stored anywhere? Can anyone verify that? I've only gotten the last thing I entered for a while now.
Click to expand...

Not a safety thing, a stack thing. If you replay a previous stack position, you lose the rest of the stack.
To demonstrate, in debug console, type:
1<enter>
2<enter>
3<enter>
4<enter>
up/down arrows show all four commands.
re-run #2 (up-up-enter)
up/down arrows show only commands 1 and 2.
 
JGCMiner said:
Just throwing this out there...

Given that there still seems to be some bugs with the current version, wouldn't it be better just to re-release the 0.11.1.25 wallet with the new name DASH and the new css theme tomorrow -- and leave the coding fixes/improvements in 11.2.x for later?

I don't think we want a big clalamity and 4 or 5 fixes released on the day we officially rebrand.
Click to expand...
Where have you been... LOL that isn't how we do things around here.
 
coingun said:
Where have you been... LOL that isn't how we do things around here.
Click to expand...

Quite true. :tongue:

However, I was just hoping that we had learned from past spectacles and this time took a more moderate approach especially since a lot of eyes are on us during this rebranding process.

It was just a sugesstion. I will leave those in charge to decide what is best. :cool:
 
You must log in or register to reply here.
Back
Top