&zzz
+FreefallHeavens
+R4SAS
+RN
+StormyCloud
+T3s|4
+acetone
+cims
+eche|off
+fa
+mareki2p
+nilbog
+orignal
+postman
+qend-irc2p
+rednode
+snex
+wodencafe
Arch
Danny
Irc2PGuest28384
Irc2PGuest66257
Irc2PGuest75631
Irc2PGuest81267
Onn4l7h
Onn4|7h
Over
ReturningNovice
Sisyphus_
Sleepy
T3s|4_
U1F642
Watson
Zapek
aargh4
ahiru
ananas
anontor
calamares
dr4wd3
dr|z3d
duanin2
i2potus
ice_juice
justaperson
luvme
mahlay
makoto
marek22k
n2_
not_bob_afk
onon_
pinotto
poriori
profetikla
psychopuck
r00tobo
rapidash
test7363673
uop23ip
w8rabbit
x74a6
zelgomer
eyedeekay
OK that might be enough to fix gitea for us... if it is I'll write us a postmortem, if it isn't I'll hold off on the postmortem until I actually fix it
eyedeekay
will be back in a few minutes after the backups run
eyedeekay
Well it's not actually fixed but it looks a lot more fixed, downtime should be a lot less noticable
dr|z3d
translation: "I didn't fix it as such, I just threatened it."
eyedeekay
unironically yes
dr|z3d
:)
eyedeekay
Whackamoling deadlocked git subprocesses keeps gitea from crashing too much and speeds up rebooting, that + a caching proxy