Closed Ernest314 closed 11 months ago
Turns out it was caused by initializing from invalid timezone strings...
There's a weird (unfortunate) mismatch between Windows/Linux Timezone IDs (windows vs. IANA), which may have been the cause it only worked on my local machine? Either way, should be fixed with a00a095c590959f0682e18cccee614eca217cb55
This just randomly started happening (see logs from 2023-01-09)--the client seems to be heartbeating, but does not respond to any commands. Subsequent restarts seemed to show that crafter data was never initialized, but eventually it started working on my local machine (while still being broken server side). All this happened with seemingly no code changes.