A bug
A random bug that crashes the ENTIRE server.
Explanation
At first, I saw a crash happening – no error message, just that the server is using a closed connection, which means a disconnected player which was caused by a bug, but I had no idea what was wrong.
Did a few things, tweaked a few lines, thought it’d be fixed, started working on the next item on my TODO list as usual.
But then, suddenly, while testing, it crashed when I tried to create a clan. Why? How? No idea.
Same thing once again, no error message.
Looked into it for 20 minutes. No idea what’s wrong. Panicking. What do I do?
Then I thought of Copilot. So I told the whole story to copilot.
Copilot thought for about 31 minutes 17 seconds. Checking every line, some, even twice for some reason. Then, after all that, it made a few changes, all less than 3 lines.
That’s it.
That’s the story of how I added Copilot to the AI usage of my project
And to be fair, I thought of increasing the timeout on the database just a couple hours ago. But then I forgot, which lead to my doom apparently. Well, I’m not dead. But you know what I mean.
Flashback
A few hours ago, I noticed that sometimes when I tried to log in, the server would see a database is locked (5) (SQLITE_BUSY) error message. I ignored it because I thought it’d be fine. Boy was I wrong.
Perhaps this is a side effect of spawners adding items and entities periodically… But then, it’s been a while since spawners were introduced.
Conclusion
Regardless, that was traumatizing. I was worried for my life (I’m scared of bugs).
Now, it looks like everything is working fine. I need to get back on the grind. Though, I’ve completely forgotten what I was doing before this devastating situation happened.
Ciao!
pic: summary of copilot’s changes, even tho only the first change was relevant.