• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

v0.10.12.x RC4 Testing

Status
Not open for further replies.
Question: "Amount of Darkcoin to keep anonymized: 1000".
Does it mean if you have less than 1000 drk in your wallet, DS should stop seeking for entries to denominate? My wallet showed it kept locking some amounts, yet none of the amount (less than 1000) was denominated, and I could not send coins using Non-Anonymous Funds, had to wait until DS Status said "Idle" to do it.
 
Running wallet by command line (./darcoin-qt -testnet=1) and noticed that every time I open option dialog it writes "QMetaObject::connectSlotsByName: No matching signal for on_resetButton_clicked()" in console.
 
Running wallet by command line (./darcoin-qt -testnet=1) and noticed that every time I open option dialog it writes "QMetaObject::connectSlotsByName: No matching signal for on_resetButton_clicked()" in console.
You need to put "& disown" at the end of your command line. Without the quotes
 
Running wallet by command line (./darcoin-qt -testnet=1) and noticed that every time I open option dialog it writes "QMetaObject::connectSlotsByName: No matching signal for on_resetButton_clicked()" in console.
You can ignore that warning.

You need to put "& disown" at the end of your command line. Without the quotes
Should work without.

Thanks for that one! But doesn't this means that there is something wrong with that dialog itself too?
No.
 
I really feel like to make a plea with Evan not to release RC4 today or tomorrow. We are so close to make DRK perfect. The market/supporters have been supporting and waiting this far, they can wait for a few more days. What do you guys think?
 
I really feel like to make a plea with Evan not to release RC4 today or tomorrow. We are so close to make DRK perfect. The market/supporters have been supporting and waiting this far, they can wait for a few more days. What do you guys think?

I agree. Any issues we are having in this thread are going to be 10x worse on mainnet and it wouldn't be good to have another calamity at launch. However, I also think that Evan knows this and won't release until the users in this thread aren't reporting bugs.
 
I don't know Evan or any of the devs but I find it highly unlikely that they will be releasing RC4 until they have done everything they possibly can to ensure stability. We're all in this together.

However...there are some issues IMHO that will not be found in testnet. There will be minor fixes after release. This has to be expected.

I haven't seen any official statements about release dates anyway.
 
I don't know Evan or any of the devs but I find it highly unlikely that they will be releasing RC4 until they have done everything they possibly can to ensure stability. We're all in this together.

However...there are some issues IMHO that will not be found in testnet. There will be minor fixes after release. This has to be expected.

I haven't seen any official statements about release dates anyway.

At the time of the last update Evan mentioned "Monday or Tuesday", but I don't think he expected as many issues as were found in the last 24 hours.
 
flare
Do you already have something drafted? Can we already plan something to make sure as many of us are available?
Very rough, something like this - times not adjusted to our 24h work calendar yet :D

upload_2014-8-11_17-26-21.png
 
****** Please Update To 10.12.20 or 9.12.20 *******

We should be good to go. Let us know if there's anything critical that still needs to be fixed before launch. Otherwise, I'll merge into master later on today.

PS. It's still possible to get charged collateral, because this update is backwards compatible and masternodes are in the process of updating.

- Disabled collateral charging for now. We'll work on this after RC4 is released and update the masternode network after it's working properly. It's not incredibly important at this stage (while we're closed source), so I don't want it holding up the release. Plus it's really the only issue we're experiencing
- Merged rebroad's (https://github.com/rebroad) changes to bring debugging output more in line with the bitcoin project. Output is now much cleaner and can be split by category.
- Removed some debug messages
- Merged mac/windows build icons
- Fixed windows "Apply" configuration bug

Stable Binaries
http://www.darkcoin.io/downloads/master-rc4/darkcoin-qt
http://www.darkcoin.io/downloads/master-rc4/darkcoind

RC4 Binaries ( masternodes / auto-denom )
http://www.darkcoin.io/downloads/rc4/darkcoin-qt
http://www.darkcoin.io/downloads/rc4/darkcoind
 
Last edited by a moderator:
****** Please Update To 10.12.20 or 9.12.20 *******

We should be good to go. Let us know if there's anything critical that still needs to be fixed before launch. Otherwise, I'll merge into master later on today.

- Disabled collateral charging for now. We'll work on this after RC4 is released and update the masternode network after it's working properly. It's not incredibly important at this stage (while we're closed source), so I don't want it holding up the release. Plus it's really the only issue we're experiencing
- Merged rebroad's (https://github.com/rebroad) changes to bring debugging output more in line with the bitcoin project. Output is now much cleaner and can be split by category.
- Removed some debug messages
- Merged mac/windows build icons
- Fixed windows "Apply" configuration bug

Stable Binaries
http://www.darkcoin.io/downloads/master-rc4/darkcoin-qt
http://www.darkcoin.io/downloads/master-rc4/darkcoind

RC4 Binaries ( masternodes / auto-denom )
http://www.darkcoin.io/downloads/rc4/darkcoin-qt
http://www.darkcoin.io/downloads/rc4/darkcoind

getting debug messages in the console with this update

edit: Evan, pretty sure this is critical. debug is coming to the standard output.
 
Last edited by a moderator:
getting debug messages in the console with this update

edit: Evan, pretty sure this is critical. debug is coming to the standard output.
actually debug messages are now splited between standard output and debug.log: masternodes messages comes to stdout only and connection messages comes to debug.log only
 
Status
Not open for further replies.
Back
Top