@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+Stormycloud
+cumlord
+dr|z3d
+eche|off
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
BubbRubb
Chrono
Dann
DeltaOreo
Irc2PGuest22388
Irc2PGuest43747
Irc2PGuest68968
Irc2PGuest70600
Irc2PGuest74352
Irc2PGuest76942
Onn4l7h
Over
Sisyphus
Sleepy_
T3s|4_
Teeed
aargh1
ac9f_
acetone_
b3t4f4c3__
bak83_
combed_tree328
coolbuddy799
dr4wd3_
duanin2
duck
leopold
makoto
not_bob_afk
poriori
profetikla
r00tobo
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
vivid_reader56
w8rabbit
x74a6
xHarr
zzz
good morrning eyedeekay, where are we at with the broken PRs?
eyedeekay
Recreating them is where I am at, I have tried everything I or gitea forum or issue log can to regenerate the PR data and I can see if on the 'file PR' side but in the PR's themselves it doesn't show up
eyedeekay
But repo health checks are passing again and recreating them seems to work
zzz
ok, ofc I can just re-push them to a new branch, or the current branch, or we can abandon PRs and just check things in to master locally
zzz
3 weeks into the cycle, not raising the alarm yet, but at some point the schedule's going to be in jeopardy
eyedeekay
Same branch seems to work but I need to close them to do that, if you want it might help to branch again and name them them something like zzz-jetty12-2
eyedeekay
Close+reopen doesn't work either, it's close+re-file only
zzz
ok but don't say maybe, if you want me to do something tell me and I'll do it
eyedeekay
OK then go ahead and do that thing, just check out the branch, `git checkout -b $oldname-2` and `git push origin $oldname-2`
zzz
ok I'll do that for jetty12 (pr 512) that you closed
zzz
what about 519 that was broken, and also 523, 521 that I would like to get in, maybe 498 too
eyedeekay
All of them please
zzz
ok
zzz
branched and pushed, now the same old problem, getting a 500 internal server error trying to create the PR
eyedeekay
What the hell, OK I am on it
eyedeekay
OK it's just more dangling lockfiles I guess I missed some from the whackamole
eyedeekay
I'll create the PR's after I fix it, just push the branches for me then I'll take it from there
eyedeekay
Nope, wasn't dangling from before, I know for sure I got that one, but it is a lockfile issue, maybe I can see what caused it this time...
eyedeekay
zzz I have the 500 fixed and can recreate any PR's, I am going to try something that involves pushing to one of your PR branches to resolve the merge conflict, wanted to let you know in advance of doing it
eyedeekay
Oh. Now I see.
dr|z3d
light at the end of the rabbithole, eyedeekay? :)
eyedeekay
Maybe
eyedeekay
Chasing some clues about why the new checkins don't appear in the PR's
dr|z3d
did you run the fix repos job you were talking about the other day that was going to take a couple of hours?
eyedeekay
Yup, and it seems to have worked, I can run git fsck again
dr|z3d
good stuff, that's progress then. and I haven't seen any more 503s, either, so the clearnet mitigations appear to be working pretty well.
dr|z3d
did you suggest zzz just nuke the PR and resubmit, or all PRs are currently being met with fail?
eyedeekay
nuke and resubmit is what we're going with but new PR's are still stuck with the checkins from time-of-creation, new ones never appear
dr|z3d
and you've tried nuking the problematic checkin(s) as well, or just pushing a known good revision with --force?
eyedeekay
Yeah it looks like it's a webhook thing
eyedeekay
git will 502 for a few minutes