[09:57:55] I know noone is working today, but If anyone is for some reason around I'd love a merge of https://gerrit.wikimedia.org/r/c/operations/docker-images/production-images/+/619731 :P [09:59:45] addshore: oh, sorry. I was not fully aware that you can't merge it yourself [10:00:39] I indeed cant :) [10:01:15] ty! [10:01:27] also, stop working, your on holiday arent you? :P [10:01:45] na, I'm based in germany :) [10:02:15] aaaah, nice! I'm in the Uk working for germany but I mostly end up taking german holidays :P [10:02:31] can you build the image yourself or should I do it? [10:02:47] I also believe I can't do that (I was assuming it was automatic until you said that) [10:03:06] (sorry, don't know where the boundaries are here) [10:03:25] no problem. Will do in a sec [10:12:16] <3 [10:29:04] addshore: templating...always fun. We missed out on https://gerrit.wikimedia.org/r/c/operations/docker-images/production-images/+/620302 [10:29:50] ooof, shouldnt that be caught by a linter? :P [10:30:15] definitely :) [10:34:17] <_joe_> addshore: that repo still shamefully has no CI setup [10:34:23] <_joe_> if anyone could contribute it... [10:34:26] :D [10:34:35] I might be able to help out with that tbh :P [10:37:58] addshore: Your image should be available by now [11:02:33] 10serviceops, 10Operations, 10Platform Engineering, 10Wikidata, 10Sustainability (Incident Followup): mw* servers memory leaks (12 Aug) - https://phabricator.wikimedia.org/T260281 (10NullPointer) I suggest setting this a security issue since this may cause people to //intentionally// make memory leaks to... [11:05:55] jayme: thanks! [11:09:43] 10serviceops, 10Operations, 10Platform Engineering, 10Wikidata, 10Sustainability (Incident Followup): mw* servers memory leaks (12 Aug) - https://phabricator.wikimedia.org/T260281 (10RhinosF1) >>! In T260281#6385334, @NullPointer wrote: > I suggest setting this a security issue since this may cause peopl... [11:12:50] jayme: turns out I also need build-essential so might make another PR..... [11:13:24] Or I should make a different base image for the "mwcli" for use in CI? But per the discussion yesterday the golang image is a dev image anyway, so it should probably have build-essential in it too [11:15:20] addshore: I guess thats added by the other images using golang as builder as well. Maybe you could have a look what else they have in common (I suspect git for example) and add that as well [11:16:15] yup, will do [11:20:47] I feel slightly evil not including these packages in the 1.11 image, but it doesnt look like that is really used any more... [11:22:28] addshore: I dont think thats a problem. People are free to upgrade to the 1.13 image ;) [11:22:40] 2 new patches up :) [11:32:45] Thanks. Will take a look after lunch [14:03:03] addshore: rebuild is done [14:55:11] 10serviceops, 10Operations, 10Platform Engineering, 10Wikidata, 10Sustainability (Incident Followup): Figure what change caused the ongoing memleak on mw appservers - https://phabricator.wikimedia.org/T260329 (10JMeybohm) Looking at the values today it's pretty clear that mw1382 wins and mw1381 takes the... [14:59:17] effie: rzl: wkandek: you're okay with that? ^ [15:00:19] jayme: rzl is off today and maybe wkandek is too -- but it SGTM [15:00:55] ah, yeah. Forgot about the holiday. Thanks [15:38:41] I will be around PST afternoon and can reboot. [20:18:48] 10serviceops, 10Operations, 10Growth-Team (Current Sprint), 10Patch-For-Review, 10User-Elukey: Reimage one memcached shard to Buster - https://phabricator.wikimedia.org/T252391 (10kostajh) > @kostajh -- are you asking whether we should deactivate EditorJourney in all wikis, so as to stop it from recordin...