01:08 aardvark: can you add this to the main package https://gitlab.freedesktop.org/xdg/shared-mime-info/-/commit/76b82a43bf4fa141daa2dcbc88bf6f0fedcbe5c6 thanks
01:11 aardvark: or an update
01:15 sstac: please, update if possible
02:21 alanc: aardvark: as the channel topic says, this channel is for the freedesktop hosting service, not all the individual projects hosted there - you'll need to reach out to that project's maintainers to request changes from them
02:22 alanc: should probably update the IRC section of https://www.freedesktop.org/wiki/GettingInvolved/ to make that clearer
02:25 alanc: that commit appears to be in the 2.4 release though
10:35 sstac: I have an issue with changing mime type of a file, may i ask here?
11:20 bentiss: If anyone sees project tokens or group tokens disappearing -> https://gitlab.com/gitlab-org/gitlab/-/issues/521001 should be fixed in a next gitlab update
11:36 mupuf: bentiss: thanks, I guessed this was something like that and added an expiration date instead :D
11:53 martink: heya, it seems I've lost the ability to trigger/run pipelines on my own mesa clone. here's a dummy commit that refuses to pick any pipelines https://gitlab.freedesktop.org/blu/mesa/-/commit/69103881af054a513c51810de35f5ec6a366afa8
12:03 hakzsam: gitlab seems to have issues, I force-pushed an update to eg. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/28988 1h ago but it's still not up-to-date
12:05 martink: hakzsam, thanks for the heads-up
12:38 eric_engestrom: mupuf: just told me about the same thing, he pushed commits but gitlab is not updating the MR
12:40 mupuf: daniels, bentiss: Are there workers that may need to be kicked a little?
12:42 bentiss: It seems that everybody is running Ci::DestroyOldPipelinesWorker and the background jobs are piling up (3856 enqueued)
12:42 bentiss: I flushed them this morning, but looks like I need to spin up more sidekiq
12:44 bentiss: alright, the queue is draining
12:46 mupuf: bentiss: sweet, thanks
12:48 bentiss: FWIW, as soon as we start putting the ezpiration rule for the pipline, it starts, but this is *really* slow, but it does the job
12:55 DragoonAethis: bentiss: there probably have been more important things happening, but did you have any time to benchmark the new servers GitLab will be migrating to, how fast storage, git ops are on the new hosts etc?
12:57 bentiss: DragoonAethis: still in the process of evaluating the deployment (like being able to deploy)
12:58 bentiss: I just ordered (and received) 2 temp servers for the db, so I'll be able to try deploying the db on 3 bare metal servers, connected to the rest of the cluster (in the cloud part of hetzner)
12:59 DragoonAethis: bentiss: alright, gl hf!
13:21 alyssa: bentiss: et al: btw, thank you for your tireless (or tired?) work with the gitlab migration :)
13:21 bentiss: thanks :)
13:22 alyssa: i have scheduled a holiday during the planned migration time so i am in an excellent position to say, take all the time it takes to get it right and make sure you take breaks ;P
14:07 svuorela: will gitlab be gone or read-only during downtime ?
14:07 emersion: gone
14:07 emersion: (afaiu)
14:07 svuorela: ok
15:35 Ford_Prefect: I'll have to go search for some grass to touch. But srsly, thank you bentiss and everyone else doing this hard labour <3
15:36 Ford_Prefect: So as to not pile on load, should we clean up artifacts via API instead of waiting for the automatic jobs, or just let it be for now?
15:37 bentiss: I think it'll be fine to set up the settings in the UI, once the current ones are done
15:37 bentiss: I'll keep monitoring them
16:21 bl4ckb0ne: already down 20G on artifacts here