Quote from: goatpig on September 26, 2017, 05:14:10 AM

Quote from: RustyRussell on September 26, 2017, 04:43:29 AM

- I get a flashed-up-then-gone dialog on startup. Finally caught it on video, it's "Mirroring Wallets". Is this something I should be able to click on?

To allow for the use of segwit and compressed key in p2sh scripts, I developed a whole new wallet code. This stuff is in C++ and operates as companion code to the python stuff. The goal was to no disrupt the existing, time tested code, while providing new features for those willing to run new code.

This flashing dialog is for the operation the mirrors the python wallet containers into their new, C++ implemented counterparts. These wallets are WO only, as they only need the data necessary to register the scripts with the DB and construct unsigned transactions. And no, there's nothing to click on, it is just there for report progress on the mirroring, and closes on its own. I figured I'd rather let people see something progress than silently mirror wallets, which can take up to a couple minutes on large wallets.

You will see that dialog every run because you use an imported address, and the mirroring code goes through every import each run, since there is no deterministic way to verify the mirrored wallet is still in sync with the python counterpart.

I'm not sure where to take that part of the GUI atm (if letting the dialog flash is ok, or requiring user interaction to close it is gonna piss off people real quick).

Quote

- Bump fee via right-click fails (see error below). This is my imported vanity addr 1RustyR...

Yep, I borked that when I fixed comments resolution in the main ledger.

Quote

- You told a previous user to use the RBF control dialog, hitting that gives this error (and no effect):

And apparently I borked that too... fml.

Thanks for the reports, will go over that stuff .4

Well, my tx didn't need bumping in the end. But Armory (0.96.3) seems can't detect its own txs; I think I'm going to run out of outputs soon

http://ozlabs.org/~rusty/Screenshot%20from%202017-11-27%2010-15-55.png

Re-importing the wallet didn't help; I was hoping there was a way to invoke rescanning? And trying to do a Wallet Consistency check gave a backtrace and an empty
Perform Wallet Consistency Check with both buttons greyed out:
(ERROR) ArmoryUtils.py:3192 - Error in pybkgdthread: 'unicode' object has no attribute 'walletPath'
Traceback (most recent call last):
File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 3190, in run
self.output = self.func()
File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 3127, in funcPartial
return thefunc(*args, **kwargs)
File "/usr/lib/armory/armoryengine/PyBtcWalletRecovery.py", line 1848, in ParseWallet
Progress=Progress)
File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 3218, in wrappedFunc
return func(*args, **kwargs)
File "/usr/lib/armory/armoryengine/PyBtcWalletRecovery.py", line 1695, in FixWallet
frt = fixer.ProcessWallet(wltPath, wlt, Passphrase, mode, Progress=Progress)
File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 3218, in wrappedFunc
return func(*args, **kwargs)
File "/usr/lib/armory/armoryengine/PyBtcWalletRecovery.py", line 400, in ProcessWallet
WalletPath = Wallet.walletPath
AttributeError: 'unicode' object has no attribute 'walletPath'

Thanks!
Rusty.