ChanServ changed the topic of #freedesktop to: https://www.freedesktop.org infrastructure and online services || for questions about freedesktop.org projects, please see each project's contact || for discussions about specifications, please use https://gitlab.freedesktop.org/xdg or xdg@lists.freedesktop.org
tr4gic has quit [Ping timeout: 480 seconds]
scrumplex_ has joined #freedesktop
scrumplex has quit [Ping timeout: 480 seconds]
Xe has quit [Read error: Connection reset by peer]
Xe has joined #freedesktop
alanc has quit [Remote host closed the connection]
alanc has joined #freedesktop
JanC is now known as Guest14725
JanC has joined #freedesktop
Guest14725 has quit [Ping timeout: 480 seconds]
mattst88 has joined #freedesktop
digetx has quit [Ping timeout: 480 seconds]
swatish2 has joined #freedesktop
digetx has joined #freedesktop
swatish2 has quit [Ping timeout: 480 seconds]
alpernebbi has quit [Ping timeout: 480 seconds]
alpernebbi has joined #freedesktop
<airlied> bentiss: just in case you missed it, gl down :-)
jsa1 has joined #freedesktop
<daniels> I bet it's Redis
<daniels> wa-hey ...
sima has joined #freedesktop
swatish2 has joined #freedesktop
jsa1 has quit [Ping timeout: 480 seconds]
swatish21 has joined #freedesktop
vjaquez has joined #freedesktop
swatish2 has quit [Ping timeout: 480 seconds]
swatish21 is now known as swatish2
pjakobsson_ has quit [Ping timeout: 480 seconds]
<whot> and it's back, whee!
ximion has quit [Remote host closed the connection]
pjakobsson has joined #freedesktop
alarumbe has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
pjakobsson has quit [Ping timeout: 480 seconds]
pjakobsson has joined #freedesktop
jsa1 has joined #freedesktop
<bentiss> regarding redis.... I just don't understand: initial deployment on Hetzner: 4 weeks without trouble, then one full week, then 5 days, then 3 :(
<colinmarc> their s3 product has also been unstable, right? maybe worth using aws for that stuff and peering?
<bentiss> colinmarc: I don't think it's related to Hetzner the redis problem. Either a new kubernetes version enforces the 10 GB limit when it wasn't on the old version, either a gitlab upgrade made redis consume a lot more data
<bentiss> for s3, I agree that it's not ideal. Though nuremberg seems to be less affected
<jani> DragoonAethis: that's just silly imo
alatiera has quit [Ping timeout: 480 seconds]
<pq> bentiss, today I have created a MR and it was merged without any hickup. :-)
<pq> thank you
<bentiss> \o/
<eric_engestrom> sergi, mupuf: I just realised I read my calendar wrong, and I can't make it to the meeting this afternoon :(
<daniels> colinmarc: have you ever seen redis corrupting the AOF happily?
<daniels> I was thinking this morning it would be nice to have a preflight script for the pod which would just check the db and nuke it if it was bad, but i couldn't see an arg to redis-server we could use for that
<bentiss> daniels: before redis has its data corrupted, we get a disk full error
<bentiss> so not surprising
<bentiss> an "easy" solution is to re-enable persistent disks, but that means that if the data is corrupted, we'll have to manually wipe it, which is a PITA
<daniels> we have to do that with what we have anyway
<daniels> EmptyDir still persists with the pod, so redis was fruitlessly restarting and reading the same corrupted AOF
<bentiss> yeah, the question is which size we need
<bentiss> agree
<sergi> eric_engestrom, mupuf: np see you next one, and talk here
<bentiss> daniels: one supposition I had too was that when we get the disk full issue, it might be because of a different process eating all the ram, or too much of it, and redis can't write to what's left
mvlad has joined #freedesktop
AbleBacon has quit [Remote host closed the connection]
vyivel has quit [Remote host closed the connection]
vyivel has joined #freedesktop
swatish2 has quit [Ping timeout: 480 seconds]
swatish2 has joined #freedesktop
<eric_engestrom> bentiss, daniels: is the new gitlab ssh key documented somewhere? a colleague asked me and I have no idea
<bentiss> eric_engestrom: it's shown everytime you hit on "Code -> Clone with SSH"
<eric_engestrom> oh, checking
<bentiss> oh, sorry I misread
<eric_engestrom> yeah, I was about to say that ^^
<eric_engestrom> (I'm on train wifi right now btw, my messages might be sent late and I might drop out)
<bentiss> they should be in the SSHFP dns entry
<bentiss> (don't know how to retrieve them from that field though)
<eric_engestrom> ah right
<eric_engestrom> `ssh-keygen -r ssh.gitlab.freedesktop.org` fetches that
<eric_engestrom> thanks!
<bentiss> hmm... they might not be correct
<eric_engestrom> hmm, the question is how to map from the record format to what ssh shows when connecting though
<eric_engestrom> they don't look anything alike
<bentiss> eric_engestrom: ssh-keyscan -D ssh.gitlab.freedesktop.org seems to show them based on the keysan it did
<bentiss> but it seems they are wrong
<eric_engestrom> ack
<bentiss> daniels: should we update the DNS entries for the new SSHFP as reported by `ssh-keyscan -D ssh.gitlab.freedesktop.org`?
<bentiss> eric_engestrom: and if that is correct, eventually you can add `VerifyHostKeyDNS yes` in .ssh/config and this should be good :)
<eric_engestrom> yeah, that would be good
<eric_engestrom> I guess any migration procedure that involves an ssh server should include a check that `ssh-keyscan -D` and `ssh-keygen -r` agree (that is, the fingerprint from connecting to ssh matches the fingerprint published in the dns records)
<bentiss> the weird part is I'm almost certain I kept the old keys around. So I might have messed up, but maybe SSHFP stores the DNS entry as well, or it was wrong for a long time
<eric_engestrom> I take it that it's not possible to update the dns record automatically?
<eric_engestrom> and what about the gl.fd.o/help page linked above?
<bentiss> eric_engestrom: there are tool to automatically update DNS records, but I'll probably have to write one for SSHFP, and it'll be quicker to update by hand
<bentiss> for the help page, no ideas why it's not showing the keys, but I can't tell you if it was the case previously
<svuorela> if a project want to do some additional 'extra custom ci steps, maybe with own hardware', is there a how-to document or best practices or anything ?
ity has joined #freedesktop
ity has quit []
ity has joined #freedesktop
swatish2 has quit [Ping timeout: 480 seconds]
JanC is now known as Guest14745
JanC has joined #freedesktop
Guest14745 has quit [Ping timeout: 480 seconds]
swatish2 has joined #freedesktop
<__tim> heh, freetype is inventing its own ci-templates it seems :)
kode54 has quit [Quit: The Lounge - https://thelounge.chat]
<eric_engestrom> svuorela: depends mostly on the hardware you want/have and who physically handles it
<svuorela> eric_engestrom: the custom hardware might just be some cloud data somewhere that needs access to non-public content (This is poppler (pdf library) render regression tests)
kode54 has joined #freedesktop
<eric_engestrom> "somewhere" is kinda important here :P
<eric_engestrom> but it sounds like maybe it's already exposed in some way; if it's as a gitlab runner, then you need its admin to register the gitlab.freedesktop.org instance, and then you can just add a job in your .gitlab-ci.yml like any other
<eric_engestrom> if it's not a gitlab runner, there might be tools to connect anyway, depending on what it is
swatish2 has quit [Ping timeout: 480 seconds]
swatish2 has joined #freedesktop
<svuorela> why is somewhere that important? Isn't it the same if it is in a amazon cloud or in a machine under my desk ?
tr4gic has joined #freedesktop
<daniels> bentiss: yeah, updating sshfp sounds like a good idea
<daniels> svuorela: like eric_engestrom says, what we do within the other projects is to register a new instance-wide runner with specific tags you can select to run on that. some of those are just Linux machines with magic things available (access tokens, network routes, etc), and some of those are raw hardware devices which we do full boots on
alarumbe has joined #freedesktop
Kayden has quit [Quit: Leaving]
<eric_engestrom> yep
<__tim> do you actually want to run it for all MR pipelines, or would it be enough to cover post-merge / scheduled pipelines and MR pipelines of developers/maintainers? Because in that case it might just be enough to add some kind of env vars with some access keys for the non-public documents, right? (assuming all devs have access anyway)
Kayden has joined #freedesktop
<eric_engestrom> svuorela: if you tell us a bit more about the machine you want to run on, we can help you more
<svuorela> eric_engestrom: We are very early in the figuring out phase, but it might just present itself as a webserver unfortunately (it's something someone else is building ..)
<svuorela> I'm still on a .. fact finding mission
<eric_engestrom> haha
<svuorela> trying to approach both ends (this and the people who want to build it) to figure out how to get the ends to actually meet
<eric_engestrom> you always have the option to have a "normal" software job on a generic fdo runner, which just pokes the remote device via http
<eric_engestrom> as long as the interface has a way to get progress, you can have the gitlab job poll on that
<svuorela> yeah. that's also what is at least the fallback if I don't get better ideas from my fact finding mission
swatish2 has quit [Ping timeout: 480 seconds]
Paddi4 has joined #freedesktop
Paddi has quit [Read error: Connection reset by peer]
Paddi4 is now known as Paddi
<eric_engestrom> svuorela: well, the "best" option is to install gitlab-runner on that machine and `gitlab-runner register --url https://gitlab.freedesktop.org --tag-list some-tag-you-will-use-in-your-job ...` and then your job's `script:` will be exactly what you want to run on that machine, no need for wrapping it through an http interface or anything
swatish2 has joined #freedesktop
johnny0 has joined #freedesktop
swatish2 has quit [Ping timeout: 480 seconds]
guludo has joined #freedesktop
haaninjo has joined #freedesktop
tr4gic has quit [Remote host closed the connection]
tr4gic has joined #freedesktop
ximion has joined #freedesktop
<robclark> anyone seeing issues with the new?merge_request pages returning 404 despite being logged in? This seems to happen if I access the page before logging in and then login. It's like something is getting invalidly cached?
<robclark> and in fact if I rename the branch, I can see the new?merge_request page for that branch... this smells like some caching lolz
JanC is now known as Guest14757
JanC has joined #freedesktop
Guest14757 has quit [Ping timeout: 480 seconds]
<colinmarc> <daniels> "Colin Marc: have you ever seen..." <- that's a new one for me, and I've run redis in production a few times. but never on k8s
<colinmarc> how does gitlab use redis? does it need disk persistence at all? is it just a cache or also queue etc?
<daniels> it's just a lookaside cache, can be binned at will
<bentiss> robclark: 404 should be cached for 10 seconds only in the latest deployments
<colinmarc> daniels: then why not just turn off the AOF?
<colinmarc> in my experience, redis is great when so long as you're not using disk persistence or clustering
<robclark> bentiss: hmm, I waited for more than just 10sec
haaninjo has quit [Quit: Ex-Chat]
swatish2 has joined #freedesktop
swatish21 has joined #freedesktop
swatish2 has quit [Ping timeout: 480 seconds]
tr4gic has quit [Ping timeout: 480 seconds]
swatish21 has quit [Ping timeout: 480 seconds]
tr4gic has joined #freedesktop
airlied_ has joined #freedesktop
airlied has quit [Ping timeout: 480 seconds]
fossdd has quit [Remote host closed the connection]
fossdd has joined #freedesktop
alatiera has joined #freedesktop
italove8 has joined #freedesktop
tr4gic has quit [Remote host closed the connection]
swatish2 has joined #freedesktop
jhli has quit [Remote host closed the connection]
haaninjo has joined #freedesktop
JanC is now known as Guest14766
JanC has joined #freedesktop
jhli has joined #freedesktop
Guest14766 has quit [Ping timeout: 480 seconds]
airlied_ is now known as airlied
JanC is now known as Guest14768
JanC has joined #freedesktop
Guest14768 has quit [Ping timeout: 480 seconds]
JanC is now known as Guest14770
JanC has joined #freedesktop
Guest14770 has quit [Ping timeout: 480 seconds]
mvlad has quit [Remote host closed the connection]
swatish2 has quit [Ping timeout: 480 seconds]
JanC is now known as Guest14771
JanC has joined #freedesktop
Guest14771 has quit [Ping timeout: 480 seconds]
JanC is now known as Guest14772
JanC has joined #freedesktop
Guest14772 has quit [Ping timeout: 480 seconds]
haaninjo has quit [Quit: Ex-Chat]
guludo has quit [Quit: WeeChat 4.6.1]
guludo has joined #freedesktop
sima has quit [Ping timeout: 480 seconds]
AbleBacon has joined #freedesktop
guludo has quit [Ping timeout: 480 seconds]
guludo has joined #freedesktop
alatiera has quit [Quit: Ping timeout (120 seconds)]
alatiera has joined #freedesktop
JanC is now known as Guest14775
JanC has joined #freedesktop
Guest14775 has quit [Ping timeout: 480 seconds]
jsa1 has quit [Ping timeout: 480 seconds]
guludo has quit [Quit: WeeChat 4.6.1]
D-HUND has joined #freedesktop
debdog has quit [Ping timeout: 480 seconds]
AbleBacon has quit [Read error: Connection reset by peer]
kxkamil2 has joined #freedesktop
JanC is now known as Guest14781
JanC has joined #freedesktop
kxkamil has quit [Ping timeout: 480 seconds]
Guest14781 has quit [Ping timeout: 480 seconds]
karolherbst has quit [Ping timeout: 480 seconds]
karolherbst has joined #freedesktop
JanC is now known as Guest14782
JanC has joined #freedesktop
Guest14782 has quit [Ping timeout: 480 seconds]
ximion has quit [Remote host closed the connection]
ximion has joined #freedesktop