Bug from #183 still occurring on Riichi.dev

[shinkuan]

Description:
It appears that the fix for issue #183 has not yet been deployed to the Riichi.dev production server. I encountered this exact bug during a recent match, which caused my bot to crash unexpectedly.

Game Record / Evidence:
The issue can be observed in the following game:

• https://riichi.dev/games/cdccaea1-2c72-4cf7-afc9-254d57d7c88a?266

Requests:

1. Deployment: Could you please deploy the latest version of riichienv to riichi.dev so the fix takes effect?
2. Game Annulment: Since my bot crashed due to this unresolved environment bug, is it possible to cancel or annul this specific invalid game record?

Thank you!

[smly]

@shinkuan Thank you for reporting this, and sorry for the inconvenience!

1. Deployment: I checked the deployment log, and it turns out the gameserver was deployed approximately 10 minutes after this game took place. Sorry about the gap between the release and the actual deployment!

  ● gameserver.service - RiichiLab Game Server
       Active: active (running) since Wed 2026-03-18 01:04:18 JST

The fix from #183 should now be live on riichi.dev.

2. Game Annulment: I may be able to address this by operating on the database directly while making sure it doesn't cause any inconsistencies with the leaderboard or other records. I'll look into it, though I can't make any promises. If I can't find a clean way to do it, the game record may have to stay as-is.

3. Version visibility: This incident also highlights that it would be helpful to display the running server version somewhere in the Web UI. I'll add this to the development backlog.

[shinkuan]

Thank you for looking into this so quickly!

Regarding the game annulment, please don't worry about it if it's too complicated or risks causing inconsistencies in the database. Leaving the record as-is is completely fine with me.

Also, displaying the server version in the Web UI sounds like a great addition! Thanks again for your help and hard work.