Armory 0.95 testing phase

[goatpig]

Latest commit has a fix for error code 22.

I'm getting a consistent segfault on BlockDir.HeadersFirst when running on Linux. OS X passes. However, OS X chokes on BlockUtilsBare.FCGIStack and just seems to be stuck, doing nothing for hours.

Slowing zero-ing in on the underlying bug. As soon as I have it isolated it should be easy to correct. I hope to have something tomorrow.

[goatpig]

achow101 submitted a PR to wrap all user facing strings in the tr() method, which a step required to deploy translations. As with any large Python PR, this has the potential to break a ton of GUI.

The first step before it gets merged is to review the code. I'm inviting my testers to go over the changeset and comment places that are potentially bug prone. Essentially, all this PR should be is a set of exiting GUI strings wrapped in tr().

Once this is reviewed and merged, it will need extensive GUI testing, i.e. click on everything trying to make it break.

You can see the changes here:

https://github.com/goatpig/BitcoinArmory/pull/89/files

[droark]

Latest commit has a fix for error code 22.

I'm getting a consistent segfault on BlockDir.HeadersFirst when running on Linux. OS X passes. However, OS X chokes on BlockUtilsBare.FCGIStack and just seems to be stuck, doing nothing for hours.

Slowing zero-ing in on the underlying bug. As soon as I have it isolated it should be easy to correct. I hope to have something tomorrow.

Linux does pass CppBlockUtilsTests now but DB1kIterTest gets stuck at 100 iterations. On OSX, CppBlockUtilsTests still gets stuck on FCGIStack but passes DB1kIterTest. This is standalone, with no Valgrind.

[goatpig]

Moved 0.95 to the testing branch, dev is now for 0.96 development, and won't be stable for a while.

[Nattygirl]

Hi everyone,
So I am busy testing v0.94.99 now and the first script I tried was the BDMbasics_watchBalance.py script, and I am getting this error

Traceback (most recent call last):
  File "BDMbasics_watchBalance.py", line 60, in <module>
    wlt.registerWallet(isNew=False)
  File "../armoryengine/PyBtcWallet.py", line 284, in registerWallet
    self.cppWallet = TheBDM.registerWallet(prefixedKeys, self.uniqueIDB58, isNew)
  File "../armoryengine/BDM.py", line 116, in inner
    return func(*newArgs, **kwargs)
  File "../armoryengine/BDM.py", line 246, in registerWallet
    return self.bdv().registerWallet(uniqueIDB58, prefixedKeys, isNew)
  File "../CppBlockUtils.py", line 1393, in registerWallet
    def registerWallet(self, *args): return _CppBlockUtils.BlockDataViewer_registerWallet(self, *args)
<class 'CppBlockUtils.DbErrorMsg'>: <CppBlockUtils.DbErrorMsg; proxy of <Swig Object of type 'DbErrorMsg *' at 0x7f455a913480> >

Anybody got a similar error and solved it?

[achow101]

Hi everyone,
So I am busy testing v0.94.99 now and the first script I tried was the BDMbasics_watchBalance.py script, and I am getting this error

Traceback (most recent call last):
  File "BDMbasics_watchBalance.py", line 60, in <module>
    wlt.registerWallet(isNew=False)
  File "../armoryengine/PyBtcWallet.py", line 284, in registerWallet
    self.cppWallet = TheBDM.registerWallet(prefixedKeys, self.uniqueIDB58, isNew)
  File "../armoryengine/BDM.py", line 116, in inner
    return func(*newArgs, **kwargs)
  File "../armoryengine/BDM.py", line 246, in registerWallet
    return self.bdv().registerWallet(uniqueIDB58, prefixedKeys, isNew)
  File "../CppBlockUtils.py", line 1393, in registerWallet
    def registerWallet(self, *args): return _CppBlockUtils.BlockDataViewer_registerWallet(self, *args)
<class 'CppBlockUtils.DbErrorMsg'>: <CppBlockUtils.DbErrorMsg; proxy of <Swig Object of type 'DbErrorMsg *' at 0x7f455a913480> >

Anybody got a similar error and solved it?

Start ArmoryDB in another shell. Then try again.

[Nattygirl]

Hi

So I executed ArmoryDB, and I still get the same error, I  think the problem might come from the _CppBlockUtil.so file,
which I can't view.

I also tried running armoryd.py and it gave me th same problem.

Now I am just stuck.

[achow101]

Hi

So I executed ArmoryDB, and I still get the same error, I  think the problem might come from the _CppBlockUtil.so file,
which I can't view.

I also tried running armoryd.py and it gave me th same problem.

Now I am just stuck.

Try running ArmoryQt first. There's a good chance that Armoryd and the other example scripts don't work anymore due to large architectural changes that just happened.

[Carlton Banks]

Getting the following with 1456a95:

Code:

-INFO  - 1475011271: (DatabaseBuilder.cpp:49) updated HEADERS db in 4202s
-INFO  - 1475011271: (BlockUtils.cpp:1608) Enabling zero-conf tracking 
-INFO  - 1475011459: (BDM_Server.cpp:826) unregistered bdv: c95295fcd242ae65
-INFO  - 1475011847: (BlockchainScanner.cpp:52) no history to scan
-INFO  - 1475011934: (BlockchainScanner.cpp:52) no history to scan
-INFO  - 1475012073: (BlockchainScanner.cpp:52) no history to scan

Tx scan never happens. CPU usage tanks. No other symptoms.

[achow101]

Getting the following with 1456a95:

Code:

-INFO  - 1475011271: (DatabaseBuilder.cpp:49) updated HEADERS db in 4202s
-INFO  - 1475011271: (BlockUtils.cpp:1608) Enabling zero-conf tracking 
-INFO  - 1475011459: (BDM_Server.cpp:826) unregistered bdv: c95295fcd242ae65
-INFO  - 1475011847: (BlockchainScanner.cpp:52) no history to scan
-INFO  - 1475011934: (BlockchainScanner.cpp:52) no history to scan
-INFO  - 1475012073: (BlockchainScanner.cpp:52) no history to scan

Tx scan never happens. CPU usage tanks. No other symptoms.

Your wallet is unregistering before the scan begins. Are you starting everything in the right order?

[Carlton Banks]

Uh, assuming the order is as below. In which case, yes.

1. Bitcoin
2. Armory

[Carlton Banks]

Here's a something from ArmoryLog.txt referring to a registerWallet function:

Code:

016-09-27 23:25 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2016-09-27 23:25 (ERROR) -- Traceback (most recent call last):
  File "./ArmoryQt.py", line 6637, in method_signal
    method()
  File "./ArmoryQt.py", line 6689, in completeBlockchainProcessingInitialization
    self.setupBDV()
  File "./ArmoryQt.py", line 6655, in setupBDV
    self.walletMap[wltId].registerWallet()
  File "/home/user/BitcoinArmory/armoryengine/PyBtcWallet.py", line 284, in registerWallet
    self.cppWallet = TheBDM.registerWallet(prefixedKeys, self.uniqueIDB58, isNew)
  File "/home/user/BitcoinArmory/armoryengine/BDM.py", line 116, in inner
    return func(*newArgs, **kwargs)
  File "/home/user/BitcoinArmory/armoryengine/BDM.py", line 246, in registerWallet
    return self.bdv().registerWallet(uniqueIDB58, prefixedKeys, isNew)
  File "/home/user/BitcoinArmory/CppBlockUtils.py", line 1417, in registerWallet
    def registerWallet(self, *args): return _CppBlockUtils.BlockDataViewer_registerWallet(self, *args)
RuntimeError: data is too large for fcgi packet

[goatpig]

Here's a something from ArmoryLog.txt referring to a registerWallet function:

Code:

016-09-27 23:25 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2016-09-27 23:25 (ERROR) -- Traceback (most recent call last):
  File "./ArmoryQt.py", line 6637, in method_signal
    method()
  File "./ArmoryQt.py", line 6689, in completeBlockchainProcessingInitialization
    self.setupBDV()
  File "./ArmoryQt.py", line 6655, in setupBDV
    self.walletMap[wltId].registerWallet()
  File "/home/user/BitcoinArmory/armoryengine/PyBtcWallet.py", line 284, in registerWallet
    self.cppWallet = TheBDM.registerWallet(prefixedKeys, self.uniqueIDB58, isNew)
  File "/home/user/BitcoinArmory/armoryengine/BDM.py", line 116, in inner
    return func(*newArgs, **kwargs)
  File "/home/user/BitcoinArmory/armoryengine/BDM.py", line 246, in registerWallet
    return self.bdv().registerWallet(uniqueIDB58, prefixedKeys, isNew)
  File "/home/user/BitcoinArmory/CppBlockUtils.py", line 1417, in registerWallet
    def registerWallet(self, *args): return _CppBlockUtils.BlockDataViewer_registerWallet(self, *args)
RuntimeError: data is too large for fcgi packet

apparently the one wallet is so large it created a serialized packet over the per packet 64kB limit. Will fix it at some point.

[goatpig]

Carlton Banks: your error should be fixed in testing, please pull and lmk.

[Carlton Banks]

Yep, fixed. Only obvious bug in a quick perusal of the loaded GUI is the same Wallet Properties missing addresses issue (small number of total addresses used are displayed, and total addresses generated has, therefore, the same problem. Generating more isn't the issue, and shouldn't be anyway. Coin Control displays all addresses correctly, and balance displays are unaffected anywhere).

[goatpig]

Yep, fixed. Only obvious bug in a quick perusal of the loaded GUI is the same Wallet Properties missing addresses issue (small number of total addresses used are displayed, and total addresses generated has, therefore, the same problem. Generating more isn't the issue, and shouldn't be anyway. Coin Control displays all addresses correctly, and balance displays are unaffected anywhere).

Do you mind hoping on the IRC channel to talk about that? (#bitcoin-armory on freenode)

[Carlton Banks]

Wallet Properties view missing addresses is fixed since yesterday's commits also. All my wallets have their addresses displayed correctly, tested all the filters etc

[achow101]

Wallet Properties view missing addresses is fixed since yesterday's commits also. All my wallets have their addresses displayed correctly, tested all the filters etc

Make sure that sending and receiving still work. Also, do you see the green highlight for addresses with balances? I don't.

[Carlton Banks]

Green highlight is working for me. (Debian 8.6) Can't yet confirm whether send or receive work.

[achow101]

New testing builds are available at https://github.com/goatpig/BitcoinArmory/releases/tag/v0.94.99.1-testing. If you download the binaries, make sure that you verify them. The tag and the binaries are both signed with goatpig's offline signing key.