0.96.1 testing build #4 - page 2. | Bitcointalksearch.org

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

Quote from: creamers on July 17, 2017, 03:39:08 PM

You can see it in the picture.....typed 200, but it only says 20.
As soon as I type anything <=197 is shows the correct value, otherwise like in the picture.

*edit I see that it didnt max the spendable amount cause I edited the fee. The button should be pressed automatically again when the fee is changed imo

I've replied to this already. The idea was that I wouldn't have to spend 2 days figuring this out because users could spend the extra second to press the "MAX" button once again, seeing it's a button and not a check box, therefor realizing the semantics indicate the functionality is not biding, and that it has always been this way since the MAX button was introduced.

creamers

newbie

Activity: 53

Merit: 0

You can see it in the picture.....typed 200, but it only says 20.
As soon as I type anything <=197 is shows the correct value, otherwise like in the picture.

*edit I see that it didnt max the spendable amount cause I edited the fee. The button should be pressed automatically again when the fee is changed imo

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

I don't have Flash installed so I can't watch this video.

creamers

newbie

Activity: 53

Merit: 0

While trying to create a unsigned transaction I notice this:

https://www.screencast.com/t/2hhmT0R9o

Fee rate per node is set to 197 sat/byte and it gave me a warning, so I wanted to change this and set it to Fee/Byte (Satoshi/Byte) and wanted to set it to 200.

Now it seems that it doesnt change as soon as I go above 197 in the Fee/Byte field. (In above movie is recorded)

Is this a bug or why can't I set a higher "Fee/Byte" than the current "Fee Rate per Node" ?

http://i66.tinypic.com/23tgzzl.png

gangtraet

full member

Activity: 159

Merit: 100

Quote from: goatpig on July 13, 2017, 05:09:03 AM

You do not build on RPi. You cross compiled from a Linux machine:

https://github.com/goatpig/BitcoinArmory/blob/master/r-pi/README.md

Unfortunately, that didn't work either. The configure script complains about No assembler code for CPU arm, and later Make fails because there was not Makefile in cryptopp.

gangtraet

full member

Activity: 159

Merit: 100

Quote from: goatpig on July 13, 2017, 05:09:03 AM

You do not build on RPi. You cross compiled from a Linux machine:

OK, that is undoubtedly faster

I just felt it was better that the RPi spent 8 hours compiling than I spent 4 hours figuring out how to cross compile. But I will do that now! Thanks

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

You do not build on RPi. You cross compiled from a Linux machine:

https://github.com/goatpig/BitcoinArmory/blob/master/r-pi/README.md

gangtraet

full member

Activity: 159

Merit: 100

Failed to build on Raspberry Pi

Hi,

I tried to build v0.96.0.4 on a Raspberry Pi (the git tag is v0.96.0.4 not v0.96.0.4-testing as for the other testing releases, right?).

After four hours, compilation fails. It looks like it is caused by "long long unsigned int" being different from "long unsigned int", see this paste: https://pastebin.com/xckJrHte

Some version numbers:
Autoconf 2.64
Automake 1.14.1
Libtool 2.4.2
gcc/g++ 4.9.2-10
swig 2.0.12
Rasbian 8 (the newest) based on jessie.

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

Quote from: Tmptmpbuggyguy on July 11, 2017, 08:07:46 AM

I assumed that cause when I started the 0.96 osx binary it said illegal instruction but building on my own worked fine. Maybe a dependency is using such instructions !?!?

https://github.com/goatpig/BitcoinArmory/blob/testing/cppForSwig/cryptopp/Makefile.am#L15

That stuff is completely disabled on OSX. This ought to be something else. Building yourself is always preferable at any rate, autotools should make that more accessible.

Tmptmpbuggyguy

newbie

Activity: 12

Merit: 0

OK thanks goatpig. Meanwhile I try to get my 0.96 working again.

Quote from: goatpig on July 11, 2017, 08:02:30 AM

Quote

The last provided testing build binary works not for me because it uses some CPU instructions that my hardware does not support.

That shouldn't not matter, none of these ASM optimizations are enabled on the OSX builds.

I assumed that cause when I started the 0.96 osx binary it said illegal instruction but building on my own worked fine. Maybe a dependency is using such instructions !?!?

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

Quote from: naska21 on July 10, 2017, 03:22:28 AM

Hi, should we upgrade bitcoin-qt to 0.14.2 version to run alongside with the latest 0.96.1 testing build #4, and if YES, will it run smoothly?

You can update to 0.14.2

Quote from: Tmptmpbuggyguy on July 10, 2017, 03:39:28 PM

I'm still not able to get a working build of the OS X version > Armory 0.96.0.

.

tag 0.96.0.4 is broken on OSX. That's been in testing but testing is broken atm for other reasons, so you'll have to wait.

Quote from: XCTfluid on July 11, 2017, 07:28:03 AM

Is there change log for test builds? Just can't find it now. Anyway not big deal, just curious.

The changelog in testing, but I have not updated it in a while. Crawl the commit history comments if you want to get an idea.

XCTfluid

newbie

Activity: 13

Merit: 0

Is there change log for test builds? Just can't find it now. Anyway not big deal, just curious.

Tmptmpbuggyguy

newbie

Activity: 12

Merit: 0

I'm still not able to get a working build of the OS X version > Armory 0.96.0.

Quote

can't open file '/Users/user/Desktop/Armory0.9.6.0.4-testing/osxbuild/Armory.app/Contents/MacOS/py/usr/local/lib/armory/ArmoryQt.py':

I followed all suggestions from this thread and also updated the mac os version to 10.8 in the build script. I also tried the git submodule stuff.

The last provided testing build binary works not for me because it uses some CPU instructions that my hardware does not support.

Tmptmpbuggyguy

newbie

Activity: 12

Merit: 0

Armory 0.96.0.3 is stuck and says "Building databases ... 15 Minutes".

Quote

-INFO - 1499683142: (DatabaseBuilder.cpp:268) parsed block file #248
-INFO - 1499683160: (DatabaseBuilder.cpp:268) parsed block file #252
-INFO - 1499683167: (SocketObject.cpp:350) POLLIN recv return 0
-ERROR - 1499683167: (BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO - 1499683167: (BitcoinP2P.cpp:969) Disconnected from Bitcoin node

Restarting Armory leads to "Building databases ... 48 Minutes" (not stuck).

Quote

-WARN - 1499684451: (BDM_supportClasses.cpp:1891) running 0 zc parser threads
-WARN - 1499684451: (BDM_supportClasses.cpp:1891) running 5 zc parser threads
-WARN - 1499684451: (BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN - 1499684451: (BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN - 1499684468: (BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN - 1499684468: (BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN - 1499684468: (BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN - 1499684468: (BDM_supportClasses.cpp:1891) running 35 zc parser threads
-INFO - 1499684482: (DatabaseBuilder.cpp:169) Reading headers from db
-WARN - 1499684482: (lmdb_wrapper.cpp:1175) No headers in DB yet!
-INFO - 1499684482: (DatabaseBuilder.cpp:208) Found 1 headers in db
-INFO - 1499684482: (DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1499684487: (DatabaseBuilder.cpp:268) parsed block file #1
-INFO - 1499684488: (DatabaseBuilder.cpp:268) parsed block file #2
-INFO - 1499684494: (DatabaseBuilder.cpp:268) parsed block file #3

Some time later

Quote

(ERROR) ArmoryQt.py:1188 - 3 attempts to load blockchain failed. Remove mempool.bin.
(ERROR) ArmoryQt.py:1193 - File mempool.bin does not exist. Nothing deleted.

Restarted Armory

Quote

-INFO - 1499691206: (DatabaseBuilder.cpp:268) parsed block file #33
-INFO - 1499691222: (DatabaseBuilder.cpp:268) parsed block file #34
-INFO - 1499691223: (DatabaseBuilder.cpp:268) parsed block file #35
-INFO - 1499691223: (DatabaseBuilder.cpp:268) parsed block file #37
-INFO - 1499691230: (DatabaseBuilder.cpp:268) parsed block file #38
-INFO - 1499691233: (DatabaseBuilder.cpp:268) parsed block file #39

I'm able to build the 0.96.0.4 on Mac OS but the final binary lacks of some files as mentioned earlier in this thread and is not starting. I'll try again now.

In the recent time it always takes me several hours to move funds from cold storage :/ (don't have a SSD).

naska21

hero member

Activity: 1358

Merit: 635

Hi, should we upgrade bitcoin-qt to 0.14.2 version to run alongside with the latest 0.96.1 testing build #4, and if YES, will it run smoothly?

creamers

newbie

Activity: 53

Merit: 0

Quote from: creamers on June 16, 2017, 11:54:52 AM

oke, will have to wait for the build to test it out.

*EDIT: since I started without the bitcoind and with bitcoin core in the foreground it runs without crashes.

Since build #4 it is running stable again with bitcoind in the background. Thank you for your effort!

paranoidx

full member

Activity: 146

Merit: 100

Okay it seems core wasnt running correctly in the background that 2nd time. All good now. I was able to send transaction.

paranoidx

full member

Activity: 146

Merit: 100

Rebuilt and rescanned database, it is now showing my balance and showing that it is connected.
I now get the following error when trying to send a transaction:

"The transaction that you attempted to broadcast hast timed out."
"The RPC interface in your node is disabled..."

paranoidx

full member

Activity: 146

Merit: 100

Armory .95 stopped working for me. Upgraded to .96.1 test 4.
Armory shows scanning transaction history for about 2-3 hours. It then shows 1 second remaining but never actually loads.
Armory shows it is offline. I have Bitcoin Core 14.2 running in the background. It is fully synced. I am running on Linux Mint 17.

https://pastebin.com/embed_js/Gi6U9k9i

naska21

hero member

Activity: 1358

Merit: 635

@goatpig, Hi, just downloaded sha256sum.txt.asc but it seems that it cointains only SHA256 hash for Debian version of Armory but not for armory_0.96.0.4-testing_win64 Please, renew sha256sum so that I could check win64 file Thanks in advance

Sorry, wrong info, everyrhing is OK with sha256sum.txt.asc. Just installed 0.96.0.4 and was very pleased to find that the bug previously reported by me (https://bitcointalksearch.org/topic/m.19800854) has been fixed in this build. Thanks, goatpig

Topic: 0.96.1 testing build #4 - page 2. (Read 8100 times)