&zzz
+Irc2PGuest22277
+RN
+StormyCloud
+T3s|4
+acetone
+cumlord
+dr|z3d
+mareki2p
+postman
+qend-irc2p
+snex
Arch
Birdy
BubbRubb1
Chrono
Danny
DeltaOreo
Irc2PGuest44009
Irc2PGuest63096
Irc2PGuest63496
Irc2PGuest74254
Irc2PGuest8482
Irc2PGuest88931
Irc2PGuest93823
Irc2PGuest95708
Onn4l7h
Onn4|7h
Over1
Sisyphus
Sleepy
Teeed
Yotsu
aargh2
ac9f
anontor
b3t4f4c3___
dr4wd3
duanin2
eyedeekay_bnc
leopold
makoto
n1
nilbog
onon_1
orignal
poriori_
profetikla
r00tobo
rapidash
shiver_
solidx66_
thetia
uop23ip_
vivid_reader56
w8rabbit
x74a6
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