0.94 preliminary testing phase - page 2.

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

I'll test that directly sometimes later.

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: Carlton Banks on February 26, 2016, 09:08:33 AM

An issue switching Core client between 0.12 and 0.11.2: I'm finding that building the Armory db with 0.11.2 initially, then restarting Armory using 0.12 (with all 0.12 validated blocks) renders Armory stuck at the last block the initial build using 0.11.2 had previously reached. Doing the same test, but with 0.12 providing Armory with the initial block data to build the db recognises the latest block when restarted using 0.11.2. Had this problem with builds previous to b24dcb2 also. Not sure what happens when doing 0.12.0 > 0.11.2 > 0.12.0 etc, haven't tried that

Perhaps that has something to do with bitcoin core 0.12 obfuscating the chainstate after syncs and reindexs. See the downgrade warning in the release notes.

Carlton Banks

legendary

Activity: 3430

Merit: 3080

An issue switching Core client between 0.12 and 0.11.2: I'm finding that building the Armory db with 0.11.2 initially, then restarting Armory using 0.12 (with all 0.12 validated blocks) renders Armory stuck at the last block the initial build using 0.11.2 had previously reached. Doing the same test, but with 0.12 providing Armory with the initial block data to build the db recognises the latest block when restarted using 0.11.2. Had this problem with builds previous to b24dcb2 also. Not sure what happens when doing 0.12.0 > 0.11.2 > 0.12.0 etc, haven't tried that

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: goatpig on February 25, 2016, 03:58:42 PM

Quote

I also get the same coin control problem droark mentioned in the other thread

Should be fixed now.

Introduced a new feature to rescan balances. Let's you fix balance errors without doing a full rescan, takes less than a minute on average (it's actually <1 sec on my machine). No need to wipe the DB with this commit, just try it as is.

They both appear to work now.

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

Quote

I also get the same coin control problem droark mentioned in the other thread

Should be fixed now.

Introduced a new feature to rescan balances. Let's you fix balance errors without doing a full rescan, takes less than a minute on average (it's actually <1 sec on my machine). No need to wipe the DB with this commit, just try it as is.

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: goatpig on February 24, 2016, 02:17:27 PM

Does the error persist with this version?

Quote from: goatpig on February 24, 2016, 03:42:26 PM

Pushed some more changes, make sure you pull from b24dcb2 onwards.

Working well. No problems yet.

Edit: I also get the same coin control problem droark mentioned in the other thread. Here is the traceback:

Code:

(ERROR) Traceback (most recent call last):
File "/home/andy/bitcoin/armory/BitcoinArmory/ui/TxFrames.py", line 785, in createTxAndBroadcast
ustx = self.validateInputsGetUSTX()
File "/home/andy/bitcoin/armory/BitcoinArmory/ui/TxFrames.py", line 602, in validateInputsGetUSTX
utxoList = self.getUsableTxOutList(totalSend)
File "/home/andy/bitcoin/armory/BitcoinArmory/ui/TxFrames.py", line 863, in getUsableTxOutList
utxos = cppAddr.getSpendableTxOutList(IGNOREZC)
File "/home/andy/bitcoin/armory/BitcoinArmory/CppBlockUtils.py", line 1969, in getSpendableTxOutList
def getSpendableTxOutList(self, ignoreZC=True): return _CppBlockUtils.ScrAddrObj_getSpendableTxOutList(self, ignoreZC)
RuntimeError: not implemented

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

Pushed some more changes, make sure you pull from b24dcb2 onwards.

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

Lots of changes, everybody will have to rebuild the DB from scratch.

Quote

2)I can't send coins. Am getting the following error.

should be fixed now

Quote

1)The balance isn't quite right. It's missing a few transactions here and there. Nothing in the logs that I can see.

Are you getting a different balance/ledger scanning the same datadir with another version of Armory? Is there a pattern in the missing transactions (I don't do multisig refs in this db, if you have a lot of lockbox activity you will be missing ledger entries but not balance)? I updated the top block reporting mechanic, is the new db reporting the proper top block now?

Quote

Edit: I'm getting an error about invalid varint

Does the error persist with this version?

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: goatpig on February 24, 2016, 12:09:01 AM

Quote from: achow101 on February 23, 2016, 11:18:15 PM

I am having some build problems that I can't figure out. My build output is on pastebin here: http://pastebin.com/QAVGGuui

Looks like you are missing entire parts of the C++ STL. Which compiler are you using? Also, is it C++11 compatible?

I am using gcc 5.2.1.

It looks like the problem is fixed and now I am running it for testing.

Edit: I'm getting an error about invalid varint

Code:

-DEBUG - 1456328054: (Blockchain.cpp:213) Organizing chain
-INFO - 1456328054: (DatabaseBuilder.cpp:47) updated HEADERS db in 0.311487s
-ERROR - 1456328054: (StoredBlockObj.cpp:1346) invalid varint in SSH data
-ERROR - 1456328054: (BDM_mainthread.cpp:429) BDM thread failed: invalid varint

Carlton Banks

legendary

Activity: 3430

Merit: 3080

Both 16a1569 and 3f02b93 are compiling and Db building OK for me. Now testing with Core 0.12.0 final also (still have a 0.11.2 copy of the blockchain that I will continue to test)

droark

sr. member

Activity: 525

Merit: 282

Okay. Having two problems with the OS X build.

1)The balance isn't quite right. It's missing a few transactions here and there. Nothing in the logs that I can see.

2)I can't send coins. Am getting the following error.

Code:

(ERROR) Traceback (most recent call last):
File "/Users/droark/Projects/BitcoinArmory/osxbuild/workspace/Armory.app/Contents/MacOS/py/usr/lib/armory/ui/TxFrames.py", line 785, in createTxAndBroadcast
ustx = self.validateInputsGetUSTX()
File "/Users/droark/Projects/BitcoinArmory/osxbuild/workspace/Armory.app/Contents/MacOS/py/usr/lib/armory/ui/TxFrames.py", line 766, in validateInputsGetUSTX
utxoSelect, scriptValPairs, pubKeyMap)
File "/Users/droark/Projects/BitcoinArmory/osxbuild/workspace/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/Transaction.py", line 2148, in createFromTxOutSelection
return self.createFromPyTx(thePyTx, pubKeyMap, txMap, p2shMap)
File "/Users/droark/Projects/BitcoinArmory/osxbuild/workspace/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/Transaction.py", line 2058, in createFromPyTx
cppPrevTx = TheBDM.bdv().getTxByHash(txhash)
File "/Users/droark/Projects/BitcoinArmory/osxbuild/workspace/Armory.app/Contents/MacOS/py/usr/lib/armory/CppBlockUtils.py", line 2115, in getTxByHash
def getTxByHash(self, *args): return _CppBlockUtils.BlockDataViewer_getTxByHash(self, *args)
RuntimeError: invalid blkFolder

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

That is some weird implementation of operator<< with stringstream on these compilers! I'll push that change and merge the OSX build PR in a minute.

droark

sr. member

Activity: 525

Merit: 282

Quote from: achow101 on February 23, 2016, 11:18:15 PM

I am having some build problems that I can't figure out. My build output is on pastebin here: http://pastebin.com/QAVGGuui

Same problem here. OS X. Latest Xcode (clang). Definitely C++11 compatible. (Hell, you could go up to C++14 and it wouldn't care.)

EDIT: goatpig, the following code should fix the problem.

Code:

   if (fileMap_ == MAP_FAILED) {
      fileMap_ = NULL;
      stringstream errStr;
      errStr << "Failed to create map of file. Error Code: " << errno;
      cout << errStr.str() << endl;
      throw runtime_error(errStr.str());
   }

EDIT 2: Confirmed. Armory now builds properly. Running the OS X build right now. We'll see what happens next....

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

Quote from: achow101 on February 23, 2016, 11:18:15 PM

I am having some build problems that I can't figure out. My build output is on pastebin here: http://pastebin.com/QAVGGuui

Looks like you are missing entire parts of the C++ STL. Which compiler are you using? Also, is it C++11 compatible?

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

I am having some build problems that I can't figure out. My build output is on pastebin here: http://pastebin.com/QAVGGuui

droark

sr. member

Activity: 525

Merit: 282

Just FYI, the Mac build process is borked. I plan to do a PR with an update pretty soon.

EDIT: Should have the PR up later tonight.

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

Pushed db auto repair core and progress bar support. Scan and Rebuild should work too now. Fixed the build issue as well. Progress bars are a little wacky for now, I'll look into making them smoother tomorrow.

Carlton Banks

legendary

Activity: 3430

Merit: 3080

Today's commit produces this compile error:

Code:

BlockchainScanner.cpp: In lambda function:
BlockchainScanner.cpp:235:30: error: invalid initialization of non-const reference of type ‘BlockData&’ from an rvalue of type ‘BlockData’
             return BlockData();
                              ^
Makefile:97: recipe for target 'BlockchainScanner.o' failed
make[1]: *** [BlockchainScanner.o] Error 1
make[1]: Leaving directory '/home/user/BitcoinArmory/cppForSwig'
Makefile:9: recipe for target 'all' failed
make: *** [all] Error 2

Sounds trivial to debug, but I'll leave that to those who code to live. Unless I'm doing something obviously wrong?

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: goatpig on February 22, 2016, 11:50:41 PM

Quote from: achow101 on February 22, 2016, 09:33:28 PM

I'm thinking this may also have to do with low disk space on my computer, so once I clean up some junk I will try again.

My DB is ~150MB on the mainnet. If you can't get it to scan mainnet, try the testnet, also build and run the C++ unit tests in the /cppForSwig/gtest folder and run those. Let me know if you can pass any of these and if you get errors, whether they are deterministic or random.

It looks like cleaning up my hard drive did the trick. I think that for those kinds of errors it would be useful to have something say that there isn't enough disk space available, which is what Bitcoin Core does.

RoadStress

legendary

Activity: 1904

Merit: 1007

Quote from: neuronics on February 23, 2016, 03:44:32 AM

Quote from: goatpig on February 22, 2016, 11:54:06 PM

Not accepting any donations until I have an actual release out there. I'll deal with all that stuff once the release is ready.

Respect !

Thank you for your efforts, very much appreciated.

Waiting for the release (and the donation address)

Thank you too! Words can't describe the appreciation for doing this.

Topic: 0.94 preliminary testing phase - page 2. (Read 2790 times)