0.96.4 RC1 - page 5. | Bitcointalksearch.org

Casimir1904

full member

Activity: 209

Merit: 100

Radix-The Decentralized Finance Protocol

Quote from: goatpig on November 22, 2017, 05:59:17 PM

Put the call in a try block and print the error message. Something like this:

Code:

         try:
            cppPrevTx = TheBDM.bdv().getTxByHash(txhash)
         except DbErrorMsg as e:
            print e.what()
            raise e

Btw this traceback is for code from master (0.96.3). Have you reproduced the same issue with the testing branch?

I'll build the testing tomorrow again. ( ATM its rebuilding the DB again ).

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

Put the call in a try block and print the error message. Something like this:

Code:

         try:
            cppPrevTx = TheBDM.bdv().getTxByHash(txhash)
         except DbErrorMsg as e:
            print e.what()
            raise e

Btw this traceback is for code from master (0.96.3). Have you reproduced the same issue with the testing branch?

Casimir1904

full member

Activity: 209

Merit: 100

Radix-The Decentralized Finance Protocol

Quote from: goatpig on November 22, 2017, 09:20:08 AM

It's suggesting your DB is corrupt.

Rebuild more than once in the last days...

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

It's suggesting your DB is corrupt.

Casimir1904

full member

Activity: 209

Merit: 100

Radix-The Decentralized Finance Protocol

Quote from: goatpig on November 20, 2017, 10:55:53 AM

The logs with the error backtraces should be there regardless of what version you are running now though. That's what I'm asking for.

Code:

2017-11-22 15:15:39 (INFO) -- TxFrames.py:727 - Change address behavior: NewAddr
2017-11-22 15:15:39 (ERROR) -- Traceback (most recent call last):
  File "/usr/local/lib/armory/ui/TxFrames.py", line 848, in createTxAndBroadcast
    ustx = self.validateInputsGetUSTX()
  File "/usr/local/lib/armory/ui/TxFrames.py", line 802, in validateInputsGetUSTX
    lockTime=TheBDM.getTopBlockHeight())
  File "/usr/local/lib/armory/armoryengine/Transaction.py", line 2287, in createFromTxOutSelection
    return self.createFromPyTx(thePyTx, pubKeyMap, txMap, p2shMap)
  File "/usr/local/lib/armory/armoryengine/Transaction.py", line 2196, in createFromPyTx
    cppPrevTx = TheBDM.bdv().getTxByHash(txhash)
  File "/usr/local/lib/armory/CppBlockUtils.py", line 2758, in getTxByHash
    return _CppBlockUtils.BlockDataViewer_getTxByHash(self, txHash)
DbErrorMsg:  >

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

The logs with the error backtraces should be there regardless of what version you are running now though. That's what I'm asking for.

Casimir1904

full member

Activity: 209

Merit: 100

Radix-The Decentralized Finance Protocol

Quote from: goatpig on November 20, 2017, 09:57:35 AM

Quote from: Casimir1904 on November 20, 2017, 09:52:02 AM

Maybe its because I just have a lot inputs in such transactions.

Shouldn't be related. If you're having errors, let me see the logs. The user who reported the issue confirmed the fix on his end, so you may be experiencing something different.

Ok, but that would take some time... Can't just keep testing all the time as i usual need to make transactions.
Now i'm rebuilding the db with a old version, i can go back to newer version when i moved some coins after that.

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

Quote from: Casimir1904 on November 20, 2017, 09:52:02 AM

Maybe its because I just have a lot inputs in such transactions.

Shouldn't be related. If you're having errors, let me see the logs. The user who reported the issue confirmed the fix on his end, so you may be experiencing something different.

Casimir1904

full member

Activity: 209

Merit: 100

Radix-The Decentralized Finance Protocol

Quote from: goatpig on November 19, 2017, 02:08:30 PM

I'll try with offline signing and let you know.

Edit: offline sign works too on my end. There is no version bump on the software, maybe you want to bootleg that to be sure you're running the right code:

https://github.com/goatpig/BitcoinArmory/blob/master/armoryengine/ArmoryUtils.py#L71

No luck for me so far. I'm back to an older version but currently rebuilding the DB.
Maybe its because I just have a lot inputs in such transactions.

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

I'll try with offline signing and let you know.

Edit: offline sign works too on my end. There is no version bump on the software, maybe you want to bootleg that to be sure you're running the right code:

https://github.com/goatpig/BitcoinArmory/blob/master/armoryengine/ArmoryUtils.py#L71

Casimir1904

full member

Activity: 209

Merit: 100

Radix-The Decentralized Finance Protocol

Quote from: goatpig on November 19, 2017, 12:58:30 PM

Yes both the offline and online instance need the fix.

Ok build the signer as well but seems its still starting the old one or the version wasn't updated.
Have to figure out later, its not working with the new build but maybe somehow the old version is loaded so could be a problem on my side.

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

Yes both the offline and online instance need the fix.

Casimir1904

full member

Activity: 209

Merit: 100

Radix-The Decentralized Finance Protocol

Quote from: goatpig on November 19, 2017, 10:24:29 AM

Should be fixed, try it out.

Nope, not working.
Does the signer need to be updated as well?

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

Should be fixed, try it out.

Casimir1904

full member

Activity: 209

Merit: 100

Radix-The Decentralized Finance Protocol

Quote from: goatpig on November 19, 2017, 08:33:53 AM

If you're willing to build from the testing branch I could probably have this fixed today.

I can do that.

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

If you're willing to build from the testing branch I could probably have this fixed today.

Casimir1904

full member

Activity: 209

Merit: 100

Radix-The Decentralized Finance Protocol

Quote from: goatpig on November 19, 2017, 08:07:20 AM

There was a bug reported when using several SW inputs the process would choke. I'm working on it.

Exactly, I try to move inputs from an incoming wallet where lot inputs on different SW addresses comes in.
Guess have to use non segwit inputs then for now.

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

There was a bug reported when using several SW inputs the process would choke. I'm working on it.

Casimir1904

full member

Activity: 209

Merit: 100

Radix-The Decentralized Finance Protocol

An offline transactions with Input from Segwit addresses it not recognized by the signer.
Signer and online version are both on the 0.96.4 RC1 version

goatpig

legendary

Activity: 3766

Merit: 1364

Armory Developer

0.96.3.99 is 0.96.4 RC1

Topic: 0.96.4 RC1 - page 5. (Read 14283 times)