@eyedeekay
&eche|on
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+acetone
+cumlord
+dr|z3d
+hagen
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
Arch
Birdy
Daddy_
Danny
FreefallHeavens
Irc2PGuest13449
Irc2PGuest20240
Irc2PGuest4863
Irc2PGuest57061
Irc2PGuest77260
Onn4l7h
Onn4|7h
Over1
Sisyphus
Sleepy
Stormycloud_
Teeed
aargh2
anontor
b3t4f4c3__
dr4wd3
duanin2
duck
gellegery
leopold
makoto
n1_
nilbog
noidea
not_bob_afk2
onon_
poriori_
profetikla
r00tobo_BNC
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
urist
user1
user4
vivid_reader56
w8rabbit
wodencafe2
x74a6
zelgomer
zyx
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