[v0.7.6] Ticket successfully purchased - client buyer shows 'context deadline exceeded' error

[David00]

Hey Matheus, I've heard of this scenario happening a few times in the past so I finally wanted to open a bug on it. I suspect it's something very minor. What happens is a ticket purchase will go through successfully, and certain participants will see the context deadline exceeded error.

Not all participants see the context deadline exceeded error - only some do. No errors are reported on the server matcher/side. I've attached the session log from the participant and from the server for a particular session where it happened.

dcrstmd_session.log
splitticketbuyer-2019-06-10-160724.log

[matheusd]

Normal occurrence. I'd need to see the dcrd/dcrwallet logs to verify, but basically what happened is that the user got the split transaction from the network but not the ticket, so the buyer process timed out waiting for it.

In other words: The server was able to publish the split transaction and then the ticket but the user only saw the split coming from the network and not the ticket. This is ok, since there's no guarantee that users see unmined transactions. Though thinking about it now, it might be a good idea to force users to also broadcast the transactions from their nodes so that they are more broadly distributed across the peer network.