Ticket accepted, but not added to the live ticket list - Missed

[mverrilli]

I had a missed ticket today that was interesting. This incident occurred on every wallet.

Normally, a ticket will process and look something like:

2018-03-18 04:19:35.359 [DBG] STPK: calling GetTransaction for new ticket sometickethashvalue
2018-03-18 04:19:35.365 [DBG] STPK: getticket finished for new ticket sometickethashvalue
2018-03-18 04:19:35.365 [DBG] STPK: Accepted valid voting service ticket sometickethashvalue committing 11351698035 in fees
2018-03-18 04:19:35.365 [INF] STPK: added new live ticket sometickethashvalue msa DcSomeMultisig
2018-04-04 13:06:08.693 [DBG] STPK: calling GenerateVote with blockHash someblockhash blockHeight 123456 ticket sometickethashvalue VoteBits 1 VoteBitsExtended 06000000 
2018-04-04 13:06:08.705 [INF] STPK: voted ticket sometickethashvalue (hash: somehashvalue bits: 1) msa DcSomeMultisig duration 12.50221ms (4.113196ms + 8.360113ms): success

However, in this case... the ticket was accepted, but not added (and therefore not voted). Like this:

2018-03-18 04:19:35.359 [DBG] STPK: calling GetTransaction for new ticket sometickethashvalue
2018-03-18 04:19:35.365 [DBG] STPK: getticket finished for new ticket sometickethashvalue
2018-03-18 04:19:35.365 [DBG] STPK: Accepted valid voting service ticket sometickethashvalue committing 11351698035 in fees
2018-04-04 13:06:08.705 [DBG] STPK: calling GetTransaction for spentmissed ticket sometickethash
2018-04-04 13:06:08.715 [DBG] STPK: getticket finished for spentmissed ticket sometickethash
2018-04-04 13:06:08.715 [INF] STPK: removed missed ticket sometickethash

[chappjc]

I wonder if it could be this edge case: https://github.com/decred/dcrstakepool/pull/250

Maybe check the ticket on the explorer to see if it was called to vote immediately after maturity

[chappjc]

Well, looking at the dates that doesn't seem to be it.

[mverrilli]

Right, it's not. I haven't walked through the code yet, but I plan to today. The fact that all voting wallets had the same issue seems to indicate a logical issue.