Qt: name_firstupdate isn't dequeued after successful transaction

[coldacid]

What behavior did you expect?
After a name_firstupdate transaction is sent to the network, the queued operation would be dequeued and I would receive no further requests to unlock my wallet to send a name_firstupdate.

What was the actual behavior (provide screenshots if the issue is GUI-related)?
Despite the name_firstupdate transaction being sent, added to a block, and confirmed, the Namecoin Core client continues to request that I unlock my wallet to send a name_firstupdate transaction for the same name every time a new block is mined.

How reliably can you reproduce the issue, what are the steps to do so?

1. Create a new name in the application.
2. Unlock the wallet when requested for the name_new operation.
3. Wait 12 blocks without closing the application.
4. Select "Yes" when the request to send name_firstupdate comes along.
5. Unlock the wallet.
6. When the following block is mined, the request comes along again despite the name_firstupdate operation already being in mempool or even in the newly mined block.

After step 6 this still occurs even after closing and restarting Namecoin Core.

What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)?
"Namecoin Core version nc0.13.99-name-tab-beta1 (64-bit)" from website

What type of machine are you observing the error on (OS/CPU and disk type)?

• Windows 10 Version 1709 (OS Build 17025.1000)
• Intel Core i7 4790 @ 3.60GHz
• 2TB HDD, NTFS

Any extra information that might be useful in the debugging process.
Debug log available upon request, just tell me what would need to be scrubbed for security/privacy.

[JeremyRand]

Hi, thanks for the bug report. My understanding is that this is fixed in #187 , which should be getting beta binaries posted soon (nc0.15.99-name-tab-beta1 is tagged, we're just waiting for Gitian signatures).

Cheers!