@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+eche|off
+hk
+orignal
+postman
+qend-irc2p
+segfault
+snex
+theoddone
+wodencafe
Arch
BubbRubb
Danny
DeltaOreo
FreeB
FreefallHeavens
I2PMorpheus
Irc2PGuest17184
Irc2PGuest21579
Irc2PGuest49450
Irc2PGuest59134
Onn4l7h
Onn4|7h
Sisyphus
Sleepy_
T3s|4_
Teeed
ardu
b3t4f4c3___
bak83
boonst
carried6590
cumlord
dr4wd3_
duck
eyedeekay_bnc
not_bob_afk
poriori_
profetikla
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
weko_
x74a6
eyedeekay
ripped out the last vestiges of chromium support from easy-install today, barely anybody used it, it hated edge, and chromium hated us so it's gone
eyedeekay
Sorry I didn't notice the gitea message here, but I did get it back up pretty shortly after, it was my fault, I was working on it at the time
eyedeekay
It's been up and down all day, there's a gitea bug at fault, I'll switch from nightly to stable when they do their next release
eyedeekay
But I'll keep bringing it back until then
zzz
I've been retrying, no luck yet
zzz
tag freeze in a few hours
eyedeekay
Broke again in the night, will be back up by 8 or so
zzz
ok thanks
eyedeekay
OK it's back now and I know how to keep bringing it back, hopefully will be able to get us on a fixed version today or tomorrow ahead of switching to stable
eyedeekay
I'll try and keep the up-and-down to a minimum today
zzz
++
zzz
dead again 20 minutes later
postman
how do you manage to do this ?
postman
i run a gitea myself and never had any issues with it
zzz
we just switched over, I thought to get away from the gitlab misery, hopefully just residual pain of migration, but I know nothing
zzz
but seems wrong to run a vital service on nightlies
dr|z3d
I've seen (it's been reported) a recent issue emerge with the max pull size which wasn't there before, but aside from that, gitea (pulled from head frequently) has always been rock solid for me. But then I'm not running a ton of extended features.
zzz
if everybody reports gitea is rock solid, what are we doing differently?
eyedeekay
It seems to have something to do with running a nightly and having github pull from many repos at once during the sync process
eyedeekay
I think maybe it sets a lock then a bunch of pulls end up competing for it somehow? But it deadlocks and then we get the 504
eyedeekay
If I am right I will have to restart it again at 10:04
dr|z3d
you could always cron job git pull on the less frequently updated repos, and stagger the pulls for the main ones.
eyedeekay
That will be the solution if I confirm the problem
dr|z3d
what's it pulling from, anyways, I thought it was the canonical repo?
eyedeekay
I have to wait to migrate to stable because I can't downgrade the db with gitea doctor, we started on stable but I switched to nightly so I could let clients set the host header
eyedeekay
Github is pulling from it
dr|z3d
oh, so github's repos are mirrors. ok.
eyedeekay
Everything in I2P_Developers->i2p at the top of the hour
dr|z3d
What you might want to alternatively consider instead is to push to both gitea and github _manually_ when you push.
dr|z3d
you can do that with a single push command, push to multiple repos.
eyedeekay
Everyone would need to do that, not just me
zzz
ok, I suggest between now and the release, switch to stable, fix the crons and CI, and let's be done with the problems.
dr|z3d
they would, eyedeekay, but it's as simple as providing a .git template iirc.
eyedeekay
I have to wait for gitea to have a stable release with a db version >= the current nightly to migrate unless I can find a workaround
dr|z3d
or they could just carry on pushing to gitea, and you could run a sync every 4 hours or whatever.
eyedeekay
I'm going to space the syncs out and run them less frequently
zzz
alternatively then, wait for the nightly with the fix, and then stop the nightly updates until stable is out and switch then
eyedeekay
until then
eyedeekay
Ack I will do so
dr|z3d
if you think github trying to pull everything is killing gitea, my advice would be to stop github doing that automatically and manually sync the repos. that seems to be the easiest way to fix things right now.
eyedeekay
Maybe. 20 min until I get my answer
dr|z3d
ok. you can still have github auto-pull the main i2p repo and the website, assuming you have granular control over the pull time, the rest you can just push via cron.
dr|z3d
if it's acceptable to zzz, plan c. would be to mirror the repos on gitea, and use github as the canonical repo. so you'd just push to github. bug tracker (and wiki?) could be either, you can sync those both ways I think?
eyedeekay
There's quite a lot of setup for 2 way sync and with things the way they are right now I don't want to introduce more complications
zzz
dr|z3d, no, let's stick with in-net-first principles and processes
dr|z3d
aight, zzz, thought you might say that.
eyedeekay
I also support what zzz said, and I want federated git to be a first-class application in go-i2p, to do that I need to dogfood gitea
eyedeekay
All right moment of truth...
eyedeekay
OMG I have never been so mad a service stayed up
eyedeekay
Sync's right there in the logs where it locked last time
eyedeekay
Logs keep going
eyedeekay
Site's still up
dr|z3d
LOL
dr|z3d
they'll make a comic strip about you one day, eyedeekay, mark my words :)
eyedeekay
I have an idea... there is one thing I'm doing differently than vanilla gitea which could cause a subtle deviation in the db behavior... but I really want to be able to generate a static build and just use sqlite and I might not be able to do that without doing what I'm doing
eyedeekay
I'll undo it and see what changes
eyedeekay
It really shouldn't be a problem, in fact I don't know if they even still have the option of the cgo-linked sqlite library it might always be the pure-go one
eyedeekay
make sure I'm not accidentally triggering module changes...
eyedeekay
and that bug, if it still exists, is suuuper old
zzz
strings pushed to transifex, translators please update
RN
oh... I guess I need to rename some things in my build script...
RN
i2p.i2p changed to "i2p" ?
RN
*** goes to see if there's any transition notes ***
zzz
huh?
RN
seems i2p_hackers changed to I2P_developers
RN
I think that's probably all I need to tell git to fix in my local repo
dr|z3d
should be, RN.
zzz
yup
RN
git remote set-url origin... seems to be all I needed. :)
zzz
capital D Developers
zzz
eyedeekay, reminder about this GH ticket github.com/i2p/i2p.i2p/issues/101 do you intend to address it for the release?
eyedeekay
Yup will get it done
eyedeekay
Have to pick a different JVM distribution again
zzz
or maybe just for arm64?
eyedeekay
Hm, yeah I guess I could do that yeah
eyedeekay
That'll be a lot easier in fact
zzz
would obviate retesting everything else
eyedeekay
Yeah I'll see if I can do it without creating a new Dockerfile and if I can't I'll make it Dockerfile.arm64
snex
this silliness has been creeping into a lot of projects lately
eyedeekay
It wouldn't be so bad if the base containers weren't such a moving target, picked Temurin because I thought it would be less so
eyedeekay
Well, approved, didn't pick
snex
they shouldnt be.. the base containers should contain all the arch logic. and they used to. they suddenly stopped for some reason
eyedeekay
Could just say to heck with it and go back to basing the container on Debian instead of trying so hard to keep the size down?
eyedeekay
That would be easy.
snex
how much bigger would they be? i dont even use the dockers for i2p+
eyedeekay
Oh I expect it would make a difference, I can't remember what it was before but it was on the order of 100mb?
dr|z3d
let's have a look at the issue...
dr|z3d
ok, so you're hard linking to a specific version, eyedeekay, that may well be an easy issue to fix.
eyedeekay
As long as there's an arm64 base for the new one, I didn't think there was but that was a while back when I looked at first
dr|z3d
> FROM alpine:latest AS builder
dr|z3d
is what we're using in +
eyedeekay
Where are you getting your JDK, alpine repo?
dr|z3d
> RUN apk add gettext tar bzip2 apache-ant openjdk21 git
dr|z3d
If you want to review the file: git.skank.i2p/i2pplus/I2P.Plus/src/branch/master/Dockerfile
eyedeekay
Thanks I'll see if I can adapt it