Closed ctm closed 9 months ago
This death is trivially reproducible. It's in a section of code that I didn't particularly like when I wrote it and that I like even less, now.
I'm seriously considering completely refactoring, by writing a little test project and either add exhaustive testing for some largish number of tables (e.g., 100) or random testing.
Before I do that, I'll look into fixing the existing code, though, because I don't want any crashes in the meantime.
I've deployed a stop-gap. It doesn't panic when a 7-seated table is split, but the split leaves 5 and starts a new table of 3, which is broken. However, I'm definitely replacing the code that does that with entirely new code that is much simpler.
I've rewritten the troublesome section and the new section is so clean that I'm not adding any extra testing. I'll deploy after this evening's game.
Fix the bug that caused the panic today when we were playing SOHE.