Left my machine on. Sorry if I had anything to do with it.
Oh yeah. to test.mucklet.com, everyone. I guess. Boss wolf doesn’t mind us using it. Usually?
Note: Don’t do anything you expect to be permanent there, it gets overwritten… dailyish.
I believe not. Acci question.
Yes, I believe everything is reset to the main site every midnight Central Europe time (So… an hour an a half from right now) Nothing is persistent, any rooms, character changes, etc will all revert to the main Wolfery’s state then.
I can confirm that, based on my software troubles, it at least got worse faster when that behavior started- it was a substantive difference I could watch happen in real time because all the errors showed up on my python console and ground my computer to a halt. The timing was pretty on point
That would be a good plan. You can, but they won’t stay, probably.
No they won’t, I’ve tried in the past. Or more like, I’ve done so in the past, testing Chippy, and they don’t stay as soon as the refresh happens (which it didn’t as far as I can tell)
The test might be having problems now
never mind it was updating
Yep, I was mistaken, it happens at about 1am Central Europe time, not midnight.
I bring the good news of the coming of the Rift.
The test server actually has an image from around the time of the crash: And all the characters I can see that were ‘broken’ are now fine. Which implies we just need to get the main server rebooted to fix it.
I leave for work for a few hours and reality collapses. How do I miss all the good parts?
Well that’s good news! Any way you could do it yourself?
Not currently, at least.
The only thing nicer than Wolfery is the people who keep it running.
Thank you so much to Acci, Talon, and all the others for all your hard work and close attention to the project, whether it’s up or down.
Okay. I see I choose a poor time to be away for two nights in the middle of the forest without any signal.
The core service is restarted and Wolfery is back.
The bug is fixed, the server update, and self-sweeping is no longer permitted.
Reason
Self sweeping caused a double-lock on the character, which dead-locks the “thread” (actually the goroutine).
Any other call that would try to read/write to that dead-locked character would in turn dead-lock as well, causing the issue to cascade, until service ended up unresponsive.
Self-sweeping will now show a message:
Cannot sweep yourself.
instead of deadlocking.
How do you sweep yourself? Still didn’t get it
Captain America saying “Son, just don’t” dot gif.