Armory Transaction Comments Only Take After a Restart

[Ondart]

I am running Armory 0.95 and Bitcoin Core 0.13.1. I noticed that when I add a comment in the 'Comments' field for a transaction and click OK, the change does not display. This also happens when changing an existing transaction comment. If I shutdown Armory and restart it, the comments then appear appropriately. It may be a bug. Just wanted to see if anyone else can reproduce this issue.

-Ondart

[goatpig]

I'm aware of this, fix coming for 0.95.2

[Ondart]

Goatpig,

Here is another one for you. I attempted to export my transactions to CSV and Armory produced this error in the log. It looks like transaction exports are currently non-functional.

Code:

2016-11-25 16:03 (ERROR) -- Traceback (most recent call last):
  File "/usr/lib/armory/qtdialogs.py", line 9504, in accept
    if self.createFile_CSV():
  File "/usr/lib/armory/qtdialogs.py", line 9555, in createFile_CSV
    order = order_ascending
NameError: global name 'order_ascending' is not defined

-Ondart

[Ondart]

Goatpig,

I am sure this is related to the original issue I posted but wanted to comment on it so it's on your radar for a potential future version fix. When attempting to Filter by a single wallet to view all transactions for that wallet, Armory does not display the change. Stopping and restarting Armory does not change the behavior.

-Ondart

[goatpig]

All of these are known issues.

[Ondart]

Not sure if you are aware of this one so just passing it along. I tail the bitcoin debug.log and both Armory logs periodically and noticed that when I shutdown Armory (0.95.1) that about a quarter of the time, bitcoind does not shutdown. When this happens I usually have to manually do a bitcoin-cli shutdown by hand or shut it down when I restart Armory. I figure it may cause corruption if someone is shutting down their computer and doesn't realize Armory did not shutdown the bitcoin daemon as they had expected.  Hope this helps...

[goatpig]

There are plenty of messed up scenarios where the client fails to close bitcoind in automated mode. I'm moving that functionality to the DB and rewriting it in the process for the next version. That should side step all the corner cases.