0.96.1 testing build #4

[goatpig]

Thanks for the report, will look into it.

[1715153943]

1715153943

[1715153943]

1715153943

[1715153943]

1715153943

[Casimir1904]

Thanks for the report, will look into it.

Help -> About doesn't work either.
Didn't check all menu entries.

Code:

arg(self, QString, QString, QString, QString, QString, QString, QString, QString, QString): argument 2 has unexpected type 'NoneType'

[goatpig]

Thanks for the report, will look into it.

Help -> About doesn't work either.
Didn't check all menu entries.

Code:

arg(self, QString, QString, QString, QString, QString, QString, QString, QString, QString): argument 2 has unexpected type 'NoneType'

Can't reproduce. Is this 0.96 or the testing branch? Can you show me the line # as well?

[goatpig]

@goatpig, Hi, , just upgraded my off-line Armory from 0.93.3 to 0.96.03-testing version/ Everything vent smoothly but when I did Tools==> MessageSigning/Verification==>  click select from Address Book to choose address for signing message the error window appears with the message " ArmoryQT.exe has stopped working "/ Repeated this a few times with the same result. The log is pasterbined https://pastebin.com/raw/juPni66G

Can't reproduce this either. Can you detail the steps you take?

[naska21]

@goatpig, Hi, , just upgraded my off-line Armory from 0.93.3 to 0.96.03-testing version/ Everything vent smoothly but when I did Tools==> MessageSigning/Verification==>  click select from Address Book to choose address for signing message the error window appears with the message " ArmoryQT.exe has stopped working "/ Repeated this a few times with the same result. The log is pasterbined https://pastebin.com/raw/juPni66G

Can't reproduce this either. Can you detail the steps you take?

Step-by-step: Tools==> click Message Signing/... ==> mouse pointer  on Book icon ( right near sign with Address:) and click on it ==> error window

[goatpig]

@goatpig, Hi, , just upgraded my off-line Armory from 0.93.3 to 0.96.03-testing version/ Everything vent smoothly but when I did Tools==> MessageSigning/Verification==>  click select from Address Book to choose address for signing message the error window appears with the message " ArmoryQT.exe has stopped working "/ Repeated this a few times with the same result. The log is pasterbined https://pastebin.com/raw/juPni66G

Can't reproduce this either. Can you detail the steps you take?

Step-by-step: Tools==> click Message Signing/... ==> mouse pointer  on Book icon ( right near sign with Address:) and click on it ==> error window

Nvm, figured it out. Wasn't running in offline mode.

[Casimir1904]

Thanks for the report, will look into it.

Help -> About doesn't work either.
Didn't check all menu entries.

Code:

arg(self, QString, QString, QString, QString, QString, QString, QString, QString, QString): argument 2 has unexpected type 'NoneType'

Can't reproduce. Is this 0.96 or the testing branch? Can you show me the line # as well?

Yes testing branch

Code:

Traceback (most recent call last):
  File "/usr/local/bin/../lib/armory/ArmoryQt.py", line 648, in <lambda>
    execAbout   = lambda: DlgHelpAbout(self).exec_()
  File "/usr/local/lib/armory/qtdialogs.py", line 8241, in __init__
    lblHead = QRichLabel(self.tr('Armory Bitcoin Wallet : Version %1-beta-%2').arg(getVersionString(BTCARMORY_VERSION), BTCARMORY_BUILD), doWrap=False)
TypeError: arguments did not match any overloaded call:
  arg(self, int, fieldWidth: int = 0, base: int = 10, fillChar: QChar = QLatin1Char(' ')): argument 1 has unexpected type 'str'
  arg(self, float, fieldWidth: int = 0, format: str = 'g', precision: int = -1, fillChar: QChar = QLatin1Char(' ')): argument 1 has unexpected type 'str'
  arg(self, int, fieldWidth: int = 0, base: int = 10, fillChar: QChar = QLatin1Char(' ')): argument 1 has unexpected type 'str'
  arg(self, int, fieldWidth: int = 0, base: int = 10, fillChar: QChar = QLatin1Char(' ')): argument 1 has unexpected type 'str'
  arg(self, QString, fieldWidth: int = 0, fillChar: QChar = QLatin1Char(' ')): argument 2 has unexpected type 'NoneType'
  arg(self, QString, QString): argument 2 has unexpected type 'NoneType'
  arg(self, QString, QString, QString): argument 2 has unexpected type 'NoneType'
  arg(self, QString, QString, QString, QString): argument 2 has unexpected type 'NoneType'
  arg(self, QString, QString, QString, QString, QString): argument 2 has unexpected type 'NoneType'
  arg(self, QString, QString, QString, QString, QString, QString): argument 2 has unexpected type 'NoneType'
  arg(self, QString, QString, QString, QString, QString, QString, QString): argument 2 has unexpected type 'NoneType'
  arg(self, QString, QString, QString, QString, QString, QString, QString, QString): argument 2 has unexpected type 'NoneType'
  arg(self, QString, QString, QString, QString, QString, QString, QString, QString, QString): argument 2 has unexpected type 'NoneType'

Edit:
building from your newest pushes gives:
./configure: line 18156: syntax error near unexpected token `fi'

Code:

else
  as_fn_error $? "missing swig!" "$LINENO" 5
fi
fi

Fixed that one manual but you might want to check it :-)

[goatpig]

Both fixed now.

[naska21]

Both fixed now.

fixed in what release? Should we download again  0.96.0.3 - testing and install it on the top of the older one?

[goatpig]

Fix is in the repo, no builds for it yet.

[Casimir1904]

Both fixed now.

Will pull later and report if i find other issues.

[Stroto]

Hi, I'm using test build 3.

Today I wanted to send a tx but got the error message "Coin selection failed with error: failed to select utxos"
Which is weird as I had no unconfirmed balances. Armory and Bitcoin Core are sync'd and displaying the same block number as any block explorer.

When looking in the armory log i see no mention of that at all. I send it through different methods and that is the tx armory picks up. but no mention of the error.

Code:

2017-07-04 09:11:50 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-07-04 09:11:50 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-07-04 09:11:50 (INFO) -- ArmoryQt.py:4640 - Dashboard switched to "Scanning" mode
2017-07-04 09:33:12 (INFO) -- ArmoryQt.py:4914 - New Block! : 474153
2017-07-04 09:33:12 (INFO) -- ArmoryQt.py:4922 - Current block number: 474153
2017-07-04 09:40:09 (INFO) -- ArmoryQt.py:5333 - Bitcoins Sent!
Amount:  X BTC
From:    X
To:      X
2017-07-04 09:43:20 (INFO) -- ArmoryQt.py:4914 - New Block! : 474154
2017-07-04 09:43:20 (INFO) -- ArmoryQt.py:4922 - Current block number: 474154

For coin selection I tried:

- first no special selection just make tx and send > error
- second select the addresses with funds > error
- third check "use all selected UTXOs" > error

what did i do wrong and/or how can I prevent or solve this?

[goatpig]

Is the fee bigger than what you are sending?

[Stroto]

Is the fee bigger than what you are sending?

i set the fee sat/b how i wanted it too and pressed "max" after that. That particular wallet had 1 income tx a few days back so only one address used. So a small kb-wise tx

I rechecked the tx i send through a different method. it looks like the fee that I set (select fee type > fee/byte) was too big (as in it exceeded the maximum funds) however i did press max after that. The only thing i can think of i did differently was putting the receiving address in after setting the fee and max. That might have caused it.

[goatpig]

Testing builds #4 are out.

[goatpig]

Try the latest builds.

[idoB]

I can confirm that the latest build, testing #4 solves the 'Export key list' error that I reported earlier (https://bitcointalk.org/index.php?topic=1957569.0)

Thanks for that, goatpig!

[wachtwoord]

I am still experiencing the memory leak problem where scanning the transactions takes a very long time. I ran it for 12 hours and it was at 4%, 1.5 month to go when I killed it. Is it helpful to let it run further?

Do you prefer I post about this in my own thread again instead of here? (I chose here because it's directly related to the #4 testing build).

[goatpig]

I am still experiencing the memory leak problem where scanning the transactions takes a very long time. I ran it for 12 hours and it was at 4%, 1.5 month to go when I killed it. Is it helpful to let it run further?

Do you prefer I post about this in my own thread again instead of here? (I chose here because it's directly related to the #4 testing build).

Use your own thread, easier to track down.

[naska21]

@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://bitcointalk.org/index.php?topic=1917955.msg19800854#msg19800854)  has been fixed in this build. Thanks, goatpig