Text interface may have shown incorrect stud cards #1495
Labels
bug
Something isn't working
can't reproduce
Can't reproduce
high priority
Should be done fairly soon
If this can be reproduced, fix whatever caused GamboMouse to see the wrong cards.
Yesterday evening, a discussion broke out when GamboMouse couldn't believe he was reraised in Razz (Hand #421590). It started with a bet, raise and re-raise on fifth street:
jrx bet and reraised because he figured his JT4xy was better than GamboMouse's QJ6wz. GamboMouse, OTOH was very surprised, because:
I've already looked at the public and private messages that were sent on this hand, and I don't see anything out of place. However, I can't actually see what GamboMouse saw, and he did have both a 3 and a 6 down.
I have not used the text interface in a long time, nor have I looked at the code for the text interface, nor are many other people using the text interface and on top of that, stud isn't particularly common, so it is possible that there's a bug in the text display of stud upcards, although I can't think of what could cause it.
I am about to disappear for a weekend where I'll be staying in a tent and won't have a lot of battery power, so I probably won't look at it this week. I have some super high priority non-programming work that I need to do (some of which I can do from my tent) and that's going to take precedence over looking at this. However…
I can look to see if there was anything weird logged for GamboMouse's connection and I can check to see if this hand was the first after a break, or the first stud hand after a game switch as well as why the board is labeled as a grid containing now cards (see public messages below). After I do that, if I don't find anything obvious, I'll strip the
high priority
label because it's the text interface. That's not fair to GamboMouse, but working on the text interface instead of doing other things isn't fair to pretty much everyone else, including Craft Poker Co.'s investors.Here are the public messages, followed with the SQL query I used to get the private messages (which I'm not posting here, because they're private):
[…]
The text was updated successfully, but these errors were encountered: