[05:24:58] akosiaris: effie: I know I'm gonna regret what I'm saying but how can I help with migrating thumbor to k8s? The reason I'm asking is that I want to add support for .bxr files (chemical notations) and that requires thumbor being able to rasterize it [05:36:57] <_joe_> Amir1: run [05:37:10] Amir1: thumbor has multiple issues one of them that it has been over a year since its last version update [05:37:37] so, that is not an easy question [05:38:04] _joe_: I know :((( [05:38:20] <_joe_> Amir1: the biggest issue is support long-term [05:38:43] <_joe_> I'm not willing to spend time in this migration without anyone outside of SRE interested in maintaining the product [05:39:04] Makes sense [05:39:44] <_joe_> we're trying to get away from the hero-model of support for this stuff [05:42:24] _joe_: In the book I mentioned, they implemented the beyonce rule which helped [05:49:52] <_joe_> Amir1: except there is no team responsible for thumbor [05:49:59] <_joe_> so there is no one to put a ring on it [05:50:15] <_joe_> and it's a fundamental piece of our infra [05:50:24] well, if it breaks then someone has to put a ring on it ;) [05:58:06] Amir1: push for someone to own it I guess? It's not the technical part that's the issue, it's the ownership. [05:59:22] noted, I will try [08:04:16] vgutierrez: heads up, I just merged https://gerrit.wikimedia.org/r/c/operations/puppet/+/726585 [08:15:56] * vgutierrez looking [08:16:37] let me trigger a puppet run on acmechief1001 for you [08:17:47] done, you got the new certs already available [08:18:45] https://www.irccloud.com/pastebin/xO5B6T2A/ [08:46:17] <_joe_> elukey: unless you object, I'll merge https://gerrit.wikimedia.org/r/c/operations/puppet/+/726915 [08:46:22] vgutierrez: thanks! [08:52:26] _joe_ sorry super late, +1 from my side [11:52:07] FYI all the stdlib update broke some spec tests, which i have now fixed, so if you have strange CI faliures try to see if a rebase fixes them [15:11:55] thanks jbond! [15:22:51] oh, nice, thanks jbond [15:23:33] thanks jbond for the after-patch support as well :) [15:24:48] np :) [15:25:36] also for casually removing ALL require_package at once :o:) [15:41:31] ^ that's awesome [15:49:13] yea, I would have probably made dozens of patches for that [15:50:02] :) [17:03:00] mhh, https://usercontent.irccloud-cdn.com/file/bZASc6M7/image.png [17:04:46] now *that* is a tempting button. [17:05:42] where is the "I don't have a problem with Wikipedia" button? [17:05:45] :) [17:07:29] zabe: fyi we had a short network issue with an upstream provider around that time, however it shuld be resolved now [17:08:09] ok, thx :) [18:12:21] Got this just now from one of my semi-automated bots I run at home: [18:12:22] > Error: Request to API failed: Error: connect EADDRNOTAVAIL 2620:0:862:ed1a::1:443 [18:12:30] which is IPv6 text-lb.esams.wikimedia.org [18:12:59] fine on retry but first time I've ever encountered that :) [18:29:22] the error, or the ed1a? :P [18:48:19] I just got a (temporary) 502 error on integration.wikimedia.org/ci, is that possibly related to the network issue from earlier? [18:48:56] kostajh: no, a 502 response means you were able to reach the server :) [18:49:22] also we believe that the network issue is completely mitigated atm [18:50:01] ok, I guess it's just Jenkins being Jenkins [18:58:52] Reedy: the error [20:12:07] Any idea on https://phabricator.wikimedia.org/T292776 [20:13:17] I think it matches with the earlier issues [20:13:33] But I'm too sleepy to do timezone conversions [20:13:48] RhinosF1: yes, almost perfectly [20:14:18] cdanis: can it be closed then? [20:17:51] I'm filing a public tracking task re: the network provider issue and I'll dupe it against that shortly [20:18:03] Thanks