Title: Please help test: version 0.5 release candidate 1 Post by: Gavin Andresen on October 10, 2011, 04:09:36 PM I just tagged the git tree "v0.5.0rc1". If you are able, please compile and help test.
See the INSTALL file at the top of the source tree for instructions on compiling. Binary releases for at least unix and mac should be available in the next day or two (there is a show-stopper bug on Windows, and we could use help from people familiar with cross-compiling using mingw to update the Windows build process). Major bugs you should be aware of: Wallet does not relock on Win32 (https://github.com/bitcoin/bitcoin/issues/571) Major changes from version 0.4: Switched from wxWidgets for the GUI to Qt, using Wladimir J. van der Laan's bitcoin-qt. Why? We didn't have any wxWidgets programmers contributing fixes or improvements. New JSON-RPC commands: getmemorypool : alternative to 'getwork' that provides everything needed to construct a block with a custom generation transaction. listsinceblock : Get all transactions in blocks since block [blockid] signmessage/verifymessage : sign/verify a message with a wallet public/private keypair Deprecated JSON-RPC features: 'midstate' data item from getwork requests Deprecated JSON-RPC commands that have been REMOVED: setlabel getlabel getaddressesbylabel getamountreceived getallreceived getreceivedbylabel listreceivedbylabel Run: git shortlog --no-merges v0.4.0.. ... to get a complete list of changes, and thanks to everybody who is contributing! Title: Re: Please help test: version 0.5 release candidate 1 Post by: jimrandomh on October 10, 2011, 08:18:13 PM Thanks for all your hard work! But does this being a release candidate mean that multi-sigs/receiver-scripts won't be available on testnet until 0.6 or later?
Title: Re: Please help test: version 0.5 release candidate 1 Post by: Gavin Andresen on October 10, 2011, 08:39:56 PM Thanks for all your hard work! But does this being a release candidate mean that multi-sigs/receiver-scripts won't be available on testnet until 0.6 or later? Hmm? testnet accepts non-standard transactions today (I've been doing some experiments with multi-sig transactions on the testnet). Title: Re: Please help test: version 0.5 release candidate 1 Post by: AlexWaters on October 10, 2011, 10:36:30 PM I am having trouble building in windows, see https://github.com/bitcoin/bitcoin/issues/581
On top of the winx64 build issue - One of my long-term goals would be to have Jenkins churn out stand-alone bitcoin.exe - they wouldn't need any dependencies and work in windows x86 and x64. (Similar to the win32-setup.exe at http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.4.0/). I believe if we make this process really automated and fluid, more people will be able to test faster. Matt has been very helpful with getting Jenkins to pull from my testing repo, and the builds are working well in Ubuntu. QT is much faster in my limited testing, and just feels better overall. Kudos to Wladimir and the others who contributed. Title: Re: Please help test: version 0.5 release candidate 1 Post by: ripper234 on October 11, 2011, 12:56:07 PM I just tagged the git tree "v0.5.0rc1". If you are able, please compile and help test. See the INSTALL file at the top of the source tree for instructions on compiling. Binary releases for at least unix and mac should be available in the next day or two (there is a show-stopper bug on Windows, and we could use help from people familiar with cross-compiling using mingw to update the Windows build process). Major bugs you should be aware of: Wallet does not relock on Win32 (https://github.com/bitcoin/bitcoin/issues/571) Major changes from version 0.4: ... Good work! Could you post/link to a list of major features? I know there are more than what you just wrote above. E.g. (assuming LiteCoin client = Bitcoin Client), the client I just downloaded a few days ago has an awesome progress bar to show how much time is needed to download the full blockchain. I can also see some more data on the blocks I mined, like when they're expected to be available in my balance. Is there anything more? (Or perhaps this was just a feature of 0.4 that I missed? I skipped that version) Also - I found something that looks like a bug with the LiteCoin version I downloaded, and I suspect it originates from Bitcoin and was not introduced in LiteCoin. I described it here (https://bitcointalk.org/index.php?topic=47417.msg567095#msg567095): Quote 1. I mined my first two blocks. 2. Tried to transfer 10 LTC to my own address. 3. Failed because of not enough confirmation "Mined balanced will be available in 118 blocks" 4. Now, the bug: I see 3 as Number of Transactions in the overview tab, but I actually have only the 2 solved blocks. 5. This persisted even after a restart of the client ... 6. Another restart - now I see 4 as Number of Transactions, still only 2 actual transactions. Where did the 3rd transaction come from? Is it a Bitcoin or LiteCoin bug? Should I report this on Bitcoin github? Title: Re: Please help test: version 0.5 release candidate 1 Post by: Luke-Jr on October 13, 2011, 11:28:38 PM Not sure what trouble BlueMatt et al are having, but I managed to build some Windows binaries. No guarantees, backup your wallet, etc...
Also, note that these aren't technically 0.5.0rc1, because I built with the very minor makefile changes made afterward (commits a1e0bb5a and e44a00ae) as well as having to hack up the build files more to make it work with my mingw setup (Gentoo crossdev i686-pc-mingw w/ GCC 4.4). I didn't bother to build with UPnP support either cuz I was too lazy to cross-compile miniupnp (and I just needed the signmessage functionality).
Title: Re: Please help test: version 0.5 release candidate 1 Post by: kwaaak on October 14, 2011, 09:28:57 PM Built on Mac OS X 10.7.2 Code: bitcoind/src/bitcoind: Mach-O executable i386 http://www.mediafire.com/?k690nwp8n661p7h Title: Re: Please help test: version 0.5 release candidate 1 Post by: justusranvier on October 14, 2011, 10:36:35 PM Everything seems to work well except than when I have "Minimize to the tray instead of the taskbar" enabled clicking on the close button doesn't do anything.
Title: Re: Please help test: version 0.5 release candidate 1 Post by: Bitsky on October 15, 2011, 09:04:30 AM Not sure what trouble BlueMatt et al are having, but I managed to build some Windows binaries. No guarantees, backup your wallet, etc... Also, note that these aren't technically 0.5.0rc1, because I built with the very minor makefile changes made afterward (commits a1e0bb5a and e44a00ae) as well as having to hack up the build files more to make it work with my mingw setup (Gentoo crossdev i686-pc-mingw w/ GCC 4.4). I didn't bother to build with UPnP support either cuz I was too lazy to cross-compile miniupnp (and I just needed the signmessage functionality).
I've tested the two QT binaries on Win2k. They start perfectly fine :) I used my real wallet.dat only with the network disabled (no offense at all, but I'll only use it with an official release). Seems there are no issues so far. Thumbs up from me. Title: Re: Please help test: version 0.5 release candidate 1 Post by: Luke-Jr on October 15, 2011, 04:38:08 PM FWIW, I am seeing reports (both my Windows binaries and also people building their own Ubuntu binaries) of 0.5.0rc1 corrupting wallets (both old and newly-made)!
Title: Re: Please help test: version 0.5 release candidate 1 Post by: Gavin Andresen on October 15, 2011, 07:08:44 PM Corrupting how? Did they install 0.5 and then downgrade (is it a backwards-compatibility issue)?
Did it get corrupted when they encrypted? Anything interesting in their debug.log? Title: Re: Please help test: version 0.5 release candidate 1 Post by: netrin on October 16, 2011, 02:00:24 AM Hey Gavin et al,
Congratulations with this RC1. My comments are mostly superficial as the plumbing seems to 'just work'. With Qt, this is the first time I've successfully compiled from HEAD for months. That's a huge bonus in my world. The incoming transaction notifications are subtle but informative. The client looks nice and lays out well full screen in xmonad 1280x800. UX failure begins in width <570px and height <226px; It needs scrollbars in small windows. Ambiguous dates (xx/xx/year) are unacceptable in an international product without localization, otherwise ISO 8601 (YYYY-MM-DD HH:mm:ss) UTC should be used. The splash-screen wallet is cute but annoying. It does not play nice with my window manager. I can't hide it, move it, nor redirect it to another workspace. So I've got this box blocking whatever I'm doing for several seconds dead center screen. I can guess, but not sure what the three icons indicate in the bottom right of the client; They could use some hover tool tips. mBTC and μBTC are clever if not hopeful as kBTC would be more realistic today :). The dynamic 'clock' unconfirmed and 'check' status are perfectly informative. I can not see the sending address in my transaction history when receiving (from unknown?). Address book, meh. In the future, I would like to see options such as import/export and more control/visibility of transactions (https://bitcointalk.org/index.php?topic=24784.0), even if these features are deactivated by default. The message "This transaction is over the size limit. You can still send it for a fee of 0.0005 BTC, which goes to the nodes that process your transaction and helps to support the network. Do you want to pay the fee?" is confusing, particularly if/when the user is sending a small amount (to him value IS the transaction). I would recommend "The network is congested" or really get into the sum(value * confirmations)/(bytes) with a "help"/"more info" link. Aside from the fact that this is confusing, it's annoying that the user has no recourse, this 'feature' makes micro-payments less realistic. I would much prefer the message warned me that miners may decide not to send such a measly amount of money without paying a fee. Would I like to send it anyway YES or no? Bitcoin is a FREE market experiment after all. A suggested transaction with vague/estimated delays might be appropriate. If the client asks for a passphrase on send, there is no need to also ask if he really intends to send coins. For small transactions, the user is unnecessarily replying yes three times before sending a coin. IFF the client must ask me if I want to send a measly amount of money to which I may decline paying a fee and thus abort, it would be better to ask for the passphrase after I've fully confirmed my intention to send (including any fees) or at the same time. Aside from my stalled micro-transaction (:) Thank Satoshi for main.h :)), everything looks and works very well! Thanks again for your hard work to produce a great client, Netrin Title: Re: Please help test: version 0.5 release candidate 1 Post by: tvbcof on October 17, 2011, 06:45:20 PM I finally got around to re-compiling on my FreeBSD system last night off of Trunk (I think :) I did it in part because I wanted to be sure I could re-compile in a hurry if need be. Binary seems to work, though I have not tried to transfer any BTC with it.
Seems that I had to include some extra system header files in protocol.cpp for AF_INET and some other symbol. I don't have the details in front of me, and I cannot say for sure that this was the fix or that I did it correctly, but after doing this I got a binary that appears to have download the blockchain as I slept and be processing transactions. Didn't even try the tests. I might be inclined to do so if someone takes enough of an interest in this platform to support it more cleanly. Title: Re: Please help test: version 0.5 release candidate 1 Post by: finway on October 18, 2011, 07:52:00 AM Under Windows 7 32bit :
The percentage showing is wrong, when i close it and reopen it to continue downloading blocks, it shows the wrong percentage number. Synchronizing with network... 8% "Catching up ... Downloaded 32076 of 149724 blocks of transaction history. Last received block was generated 658 day(s) ago." Title: Re: Please help test: version 0.5 release candidate 1 Post by: ShadowOfHarbringer on October 23, 2011, 08:30:03 PM @Gavin
Any chance for including this in 0.5.x ? https://github.com/bitcoin/bitcoin/pull/570 Title: Re: Please help test: version 0.5 release candidate 1 Post by: dooglus on October 24, 2011, 07:47:15 PM I built bitcoin-qt v0.5.0rc1 in Ubuntu 11.10 with the following packages installed and had the following problems.
Code: ||/ Name Version Description
Code: chris@chris:~/Programs/bitcoin$ apt-cache search 'libdb[0-9].*\+\+-dev'
Code: chris@chris:~$ ~/Programs/bitcoin/bitcoin-qt | uniq -c
Code: Program received signal SIGSEGV, Segmentation fault. Code: Creating accessible with different object than the original interface! Title: Re: Please help test: version 0.5 release candidate 1 Post by: dooglus on October 24, 2011, 08:13:24 PM I had bitcoin-qt crash with a "Segmentation fault" error when I tried to open the 'options' dialog. Running this command seems to have stopped the crashes: Code: sudo apt-get remove qt-at-spi Package qt-at-spi is installed by default when you install Ubuntu 11.10. It looks like this is a known bug (https://bugs.launchpad.net/ubuntu/+source/qt-at-spi/+bug/857790) in ubuntu's qt-at-spi package. You might want to include a note in the instructions about this. I had tried testing the Qt bitcoin client when it was first merged to the master branch but gave up due to these crashes. If I had known then that uninstalling qt-at-spi would fix them, I wouldn't have given up on the Qt client. Title: Re: Please help test: version 0.5 release candidate 1 Post by: Gavin Andresen on October 24, 2011, 10:51:55 PM You might want to include a note in the instructions about this. You == me? There's a sticky here about creating a pull request, it'd be most excellent if you could make you==you and fix the doc/readme-qt.rst file. I'll try hard to remember to mention this for the 0.5 release notes, but I'll warn you I'm really good at forgetting things. Title: Re: Please help test: version 0.5 release candidate 1 Post by: dooglus on October 24, 2011, 11:24:36 PM There's a sticky here about creating a pull request, it'd be most excellent if you could make you==you and fix the doc/readme-qt.rst file. See https://github.com/bitcoin/bitcoin/pull/592 Title: Re: Please help test: version 0.5 release candidate 1 Post by: dooglus on October 29, 2011, 07:12:26 AM The 'amount' column in the 'transactions' view isn't resizable, and doesn't fit in a value I recently sent.
xxx.xxxxxxxx BTC is ok, but -xxx.xxxxxxxx BTC doesn't fit, and I see xxx.xxxxx... instead (dots replacing the last 3 digits of the amount) Three figure sums probably aren't all that uncommon to be sending, and it looks pretty ugly when the value doesn't fit in the box. Title: Re: Please help test: version 0.5 release candidate 1 Post by: dooglus on November 02, 2011, 05:20:30 PM When I hover over the green checkmark in the bottom right corner, it tells me:
Code: "Last received block was generated 54 second(s) ago". I guess what the time is telling me is how much time elapsed between the block being generated and the block being received by my client, but that's not what the tooltip says. Code: "Last received block was generated 54 second(s) before it was received" Code: "Last received block was 54 second(s) old when it was received" Code: "Last received block was 54 second(s) old" Title: Re: Please help test: version 0.5 release candidate 1 Post by: cm68jd on November 04, 2011, 04:34:45 AM It looks great! The only problem is the horrible startup screen. There should be an option to disable that.
Title: Re: Please help test: version 0.5 release candidate 1 Post by: dunand on November 04, 2011, 11:04:38 AM It looks great! The only problem is the horrible startup screen. There should be an option to disable that. It could be better but it's a hundred times better than having nothing for more than one minute. Title: Re: Please help test: version 0.5 release candidate 1 Post by: Caesium on November 04, 2011, 11:45:20 AM Code: "Last received block was generated 54 second(s) ago". This may be a minor point, but "second(s)" looks SO ugly. It's a real pet peeve of mine about sites and programs that can't be bothered to clean this up. Is it really so hard to do "%d second%s", x, (x != 1 ? "s" : "") Title: Re: Please help test: version 0.5 release candidate 1 Post by: dooglus on November 04, 2011, 06:19:52 PM Is it really so hard to do "%d second%s", x, (x != 1 ? "s" : "") That's not hard, but it's not correct either. The client currently supports 7 different languages. http://doc.qt.nokia.com/qq/qq19-plurals.html talks about a better way to support plural forms in QT apps. Title: Re: Please help test: version 0.5 release candidate 1 Post by: dooglus on November 04, 2011, 06:26:22 PM Is it really so hard to do "%d second%s", x, (x != 1 ? "s" : "") That's not hard, but it's not correct either. The client currently supports 7 different languages. http://doc.qt.nokia.com/qq/qq19-plurals.html talks about a better way to support plural forms in QT apps. It turns out that's exactly what the client is using. The problem is that there's no English translation file. That should be easy to provide. I'll make a pull request. Title: Re: Please help test: version 0.5 release candidate 1 Post by: dooglus on November 04, 2011, 07:00:42 PM It turns out that's exactly what the client is using. The problem is that there's no English translation file. That should be easy to provide. I'll make a pull request. Here's an English translation that makes the strings appear correctly: https://github.com/bitcoin/bitcoin/pull/606 Title: Re: Please help test: version 0.5 release candidate 1 Post by: nibor on November 04, 2011, 10:37:08 PM Client must be near a version 1.0 if bugs like this are being fixed. :)
Title: Re: Please help test: version 0.5 release candidate 1 Post by: cm68jd on November 05, 2011, 11:56:21 PM It looks great! The only problem is the horrible startup screen. There should be an option to disable that. It could be better but it's a hundred times better than having nothing for more than one minute. Not really, because I start bitcoin on startup so now it needlessly takes over my screen for a minute when it could be started and minimizing itself to the system tray. Title: Re: Please help test: version 0.5 release candidate 1 Post by: dooglus on November 08, 2011, 10:54:10 AM I found a way to make the release candidate crash:
1. use bitcoind to send to an address that's not in the address book 2. in the client, right click the greyed-out address in the 'address' column of the transactions tab 3. 'edit label' 4. the address field is blank - would be nice if it was populated automatically. type or copy/paste the address in, and type a new label name 5. click 'ok' and get a segmentation fault Title: Re: Please help test: version 0.5 release candidate 1 Post by: mndrix on November 10, 2011, 03:16:06 PM I finally managed to build from source on OS X 10.6.8. I had to change the architecture from i386 to x86_64 otherwise I got linking errors against the libraries MacPorts built.
Anyway, the new client is very nice. I especially liked the progress bar when downloading the blockchain. That'll be great for first time users. The client stopped downloading blocks a few times (while still thousands short of the latest block), but restarting the client got it going again. I've seen the same behavior in the old client too. My only complaint about the new interface is for receiving coins. In the old interface, my receiving address was at the top of the client. To get a new address, I just clicked Copy. In the new interface, I have to switch to the Receive Coins tab, click New Address, click OK, click Copy to Clipboard. That's 4 clicks versus 1 before. I don't think it's any reason to delay the release, but it would be nice to have a more streamlined UI for a common operation like receiving coins at a brand new address. Thank you to all involved with the new UI. That even I could build it from source suggests we'll have more contributors going forward. |