When running the bot in docker the leaderboard never gets persisted since the exit handler is never hit.
So leaderboards reset with every restart.
When running the bot in docker the leaderboard never gets persisted since the [exit handler](https://github.com/SpudGunMan/meshing-around/blob/530d78482a0cc4b1bf9c81f8a7e4410bcd32112b/modules/system.py#L2428) is never hit.
So leaderboards reset with every restart.
<!-- github-sync-id:3800132991 -->
@SpudGunMan I resolved this in my deployment by adding saveLeaderboard() to the watchdog loop and removing the logging statement, but I suspect this isn't ideal.
Perhaps a persistence loop should be added to make sure all the various data sets get persisted on a schedule?
@SpudGunMan I resolved this in my deployment by adding `saveLeaderboard()` to the watchdog loop and removing the logging statement, but I suspect this isn't ideal.
Perhaps a persistence loop should be added to make sure all the various data sets get persisted on a schedule?
<!-- github-comment-id:3733677585 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When running the bot in docker the leaderboard never gets persisted since the exit handler is never hit.
So leaderboards reset with every restart.
I agree. This is happening on my end too.
@SpudGunMan I resolved this in my deployment by adding
saveLeaderboard()to the watchdog loop and removing the logging statement, but I suspect this isn't ideal.Perhaps a persistence loop should be added to make sure all the various data sets get persisted on a schedule?