&eche|on
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+eche|off
+not_bob_afk
+orignal
+postman
+snex
+wodencafe
Arch
BubbRubb
Chrono
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest16752
Irc2PGuest33667
Irc2PGuest51880
Onn4l7h
Over
Sisyphus
Sleepy_
Teeed
aargh2
ac9f_
b3t4f4c3__
b4dab00m
bak83_
duanin2
duck
john231
leopold
makoto
mareki2p_
nilbog-
poriori_
profetik1
r00tobo
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
vivid_reader56
x74a6
xHarr
dr|z3d
earth calling eyedeekay... gitea is broken.
eyedeekay
dr|zed I am currently seeing it work as well as it was last week(no push hooks running) what are you seeing
eyedeekay
Re: the push hooks I don't want to wait to get the PR's in just on the push hooks so zzz I am going to do manual merges, starting with the 2 I have already reviewed, followed by the other 4.
eyedeekay
I will do the other reviews today and reply on their PR threads and post them here. If changes are required, I will post on the PR thread and review the followup change locally. If necessary, I will make a patch and post it on the PR thread as well for transparency. After that I will do the manual merge.
eyedeekay
Once all 2.11.0 merges are complete I am going to restore gitea from a backup, re-deploy the whole thing, to get the push hooks to work again
zzz
eyedeekay, the thing is, only 519 is ready to merge
zzz
523 (sam dg2) needs your testing
zzz
512 (jetty 12) needs the eepsite migration code. as is, it will break all jetty eepsites
zzz
521 (tunnel bw limiting) needs tweaks, it's too restrictive right now
eyedeekay
Ack, then I'll start with 519, will communicate with you on the others pending review, sam dg2 I am ready to test as of this weekend with library updates so I can do that next
zzz
you already reviewed 512 right?
dr|z3d
eyedeekay: This instance is configured to run under HTTPS (by ROOT_URL config), you are accessing by HTTP. Mismatched scheme might cause problems for sign-in/sign-up.
dr|z3d
I was logged in before, can't log in any more. explore requires login.
eyedeekay
Yes I did re:512
eyedeekay
dr|zed thanks for the report, I did that to try and fix webhooks, since it isn't working I will reverse course and fix it
zzz
ok eyedeekay re: 512 I'll write the migration code and then ask what I should do
eyedeekay
dr|zed it requires a restart to fix, will do it in exactly 25 minutes
zzz
I don't want to merge w/o the migration because it will break eepsites
eyedeekay
Thanks zzz sorry about the bumps, agreed about the merge. Ping me when you are ready
zzz
late this week hopefully
eyedeekay
Ok git downtime imminent and will last a few minutes
dr|z3d
10-4, eyedeekay
eyedeekay
Just waiting on the backup to complete...
zzz
eyedeekay, the git.idk.i2p rss feed in #i2p-news is returning localhost:3000 urls
eyedeekay
Dammit. OK restart round 2, standby
zzz
fixed
eyedeekay
And it says git.idk.i2p. Hm. That means the header-based domain name auto-determination that is the reason I wanted to use gitea in the first place is working, but only if I expressly set a default domain?
eyedeekay
Something something I wonder if this is why webhooks are being so wierd...
dr|z3d
I still think all your problems go away if you just redirect clearnet to github.
dr|z3d
Put up a splash page with a 20s meta refresh explaining that for reporting bugs etc, git.idk.i2p
dr|z3d
also, you want to make sure you're not allowing inproxy access, otherwise the spiders will return.
dr|z3d
anyways, can confirm it's all working again.
dr|z3d
still broken, however -> git.idk.i2p/I2P_Developers/i2p.i2p/pulls/519
eyedeekay
Yup.