ctm
commented
9 months ago Ugh. I wound up doing some yak shaving by researching how to get a read-only Postgres connection so that when I build this tool I can use it against the production database w/o fear of accidentally altering the database. I found some relevant web pages and left them up, but never updated this issue with the information in them… and then I closed them in one of my window-closing fits.
FWIW, I'm not too tired to work on other issues, but I am going to spend a little time re-researching the read-only question before it entirely escapes my mind.
Build a tool—initially for internal use only—that replays all the messages a table window has received.
For any onlookers, be aware that mb2 does not write hole cards or other private messages to the database until the hand is over, so even when this tool is built, it will not give me the ability to see players' cards or actions during a hand.
This tool will initially be used to try to reproduce bugs, like when the UI was not updating bets (#1283), but much of the same code will later be used to allow people to see hand histories.
I'm marking this
high priority, mostly because I want to use it to try to reproduce #1283, even though I expect that particular bug to not be reproducible. However, there are tons of times where there's been a UI bug where I've been able to reproduce it either throughforce-statusor hacking up the code or I haven't bothered to reproduce because I've found it via code inspection. In each of those cases, I would have been able to do things much faster if I had this tool and writing this tool is not that hard.So, although ordering the remaining paperweights (#1201) and addressing slowness at start (#1185) are higher priorities, this'll be my work on this when I'm too tired to do other work project until it's done (or something shiny steals my attention).