Making yet another post about this because of lazy devs

[Packetdancer]

And then we bring in Dave and he finds something we missed.

This is an entire mood.

And it turns out this wasn't entirely a bug but inefficient server processing that caused a backlog, so a lot of the results weren't ready to be communicated in time for the end of the lottery. Rather than fixing a bug the solution might be improving how efficient it is.

The root cause isn't a bug, per se, but the fact that the process was not fault-tolerant is, at least in my opinion. It's an understandable one to make, given that data replication is often handled by some underlying database system and not by the game's own code directly. Still, the code surrounding it should probably have required an acknowledgment of data transferred successfully, and add things to a retry queue if it failed to get said acknowledgment, and I do think the lack there qualifies as a bug.

[MiaShino]

The root cause isn't a bug, per se, but the fact that the process was not fault-tolerant is, at least in my opinion. It's an understandable one to make, given that data replication is often handled by some underlying database system and not by the game's own code directly. Still, the code surrounding it should probably have required an acknowledgment of data transferred successfully, and add things to a retry queue if it failed to get said acknowledgment, and I do think the lack there qualifies as a bug.

Bestest part about working with databases or servers as a systems engineer, attempting to bring things up to administration. Nothing brings happiness quite like identifying potential handshaking issue with simple fix only to be informed about deadlines. You then check your notes and ohhhh right, I brought this to your attention three weeks ago and was told it would be addressed. Now I get to spend time fixing it on live deployment.. fan fricken tastic also with upper management breathing down my spine.

Became so feist inducing I spent inordinate amount of effort just self hosting everything. Fricken costly too.. fiber, hardware, heat dissipation not cheap. I may give dev team much of the feist at the times but I truly feel for whoever has been tasked with resolving this because I have been there and it stinks.

[Packetdancer]

I may give dev team much of the feist at the times but I truly feel for whoever has been tasked with resolving this because I have been there and it stinks.

Every time I have changed jobs in my life, it's been so as to try something new; there have only been a few times it was just as much to get away from the previous job as to try a new one. But my first job out of high school was as a database administrator, and that one I definitely was leaving in part to not be doing it anymore; I honestly don't think you could pay me enough to do that again.

So, you have my abject sympathy... and I definitely can also imagine the myriad possible database-related scenarios that could give rise to an issue like the placards not receiving their data.