[07:02:17] the link between cr1 codfw/eqiad is still down due to Texas' weather, no ETA to fix yet :( [07:14:15] ugh [07:43:46] good thing we have redundancy [08:43:40] 💯 if only the power grid had it though for regular households :-( [14:06:46] jbond42: I declare python bankruptcy :] [14:07:03] class MatrixArgumentFormater( [14:07:03] ArgumentDefaultsHelpFormatter, RawDescriptionHelpFormatter [14:07:06] that is a nice one [14:08:10] hashar: stolen from vola.ns [14:08:55] OF COURSE [14:09:03] jbond42: +1 [14:09:06] that is such a nice trick [14:09:14] I should learn python again [14:09:32] hashar: my change dose make this dependedn on at least python 3.6, im not sure who uses this so not sure if thats an issue? [14:09:39] I wasn't aware a class could inherit from multiple classes [14:09:52] well [14:10:05] that matrix.py is merely an helper to assist in administating user rights [14:10:05] the first classname also misspells "formatter" :) [14:10:18] I would expect most users to have a recent python installed [14:10:38] ah yeah MatrixArgumentFormater should have two T [14:10:47] ack thanks and ack will fix now thxs [14:11:15] and welcome back bblack has the weather settled down for you now? [14:11:36] fwiw the original has the right amount of Ts :-P ( https://gerrit.wikimedia.org/r/plugins/gitiles/operations/cookbooks/+/refs/heads/master/cookbooks/__init__.py ) [14:12:03] haha [14:12:12] hashar: it's a slipperly slope the multiple inheritance, I would not suggest it for normal use cases, unless there are clear contracts on what does what [14:12:31] I have already elected it python trick of the year [14:12:40] I remember I have been struggling with the exact same issue a few years ago [14:12:46] and ended up creating my own formatter [14:12:47] I ran into python multiple-inheritance many years ago, when I helped copy over Python 2.3's choice of the C3 MRO to the Perl world :) [14:12:50] or gave up maybe [14:13:24] bblack: oh hey! everything ok over there? [14:13:29] relatively speaking of course [14:14:03] yes, things are relatively-sane here now, for now! [14:18:16] py2.3 adopting C3 MRO: https://www.python.org/download/releases/2.3/mro/ -> Perl work on the same stuff (pluggable MROs with C3 as an option): https://perldoc.perl.org/mro [14:18:33] all ancient history now, and I agree multiple inheritance is rarely worth the trouble it causes! :) [14:20:54] lol [21:09:37] mutante: we need emote support in Phab so I can add a :100: token to your comment on T268946 :) [21:09:42] T268946: Offboard Pablo-WMDE from WMF systems - https://phabricator.wikimedia.org/T268946 [21:09:58] bd808: aww :) [21:10:37] I'm honestly tempted to add WMDE title block variants to https://wikitech.wikimedia.org/wiki/MediaWiki:Titleblacklist [21:11:39] (WMF) is blocked.. then (WMDE) shold be as well [21:12:02] even though the _real_ fix would be to stop using them .. yea [21:12:17] but also IF they use them, they should be blocked to prevent randoms from making them [21:18:01] mutante: that's kind of a problem on wikitech. Since the AuthManger refactor, creating wikitech accounts for others is pretty broken. So if we block the name suffix that mostly makes it impossible for anyone to use it. [21:18:17] which I'm ok with, but I don't want to just spring it on WMDE and make them upset [21:19:27] yea.. *nod*.. this is kind of another reason to stop using them. The whole idea of staff accounts would be that they can only be created by the company. [21:19:43] what are they getting out of them if they have no special meaning anyways [21:21:10] by the way.. one thing is even worse.. when you end up with "wmf" and "wmde" in actual shell accounts and LDAP [21:21:13] My sense making is that WMDE saw all of the "(WMF)" accounts and though that looked cool. Little did they know that this was really an unpopular idea that Eric capitulated to after a small number of complaints about the now long gone "staff" permissions group. :) [21:21:54] yea, afair this all started after one particular incident where a user working for WMF global banned someone or whatever it was [21:22:21] and then there was the idea we need to make it obvious which actions are official actions "by WMF" [21:22:24] I know it was brand new "policy" when I got hired mid-2013 [21:22:57] it was definitely for this very specific and limited use case where you have to make wiki edits from the office and it's directly your job to make that edit [21:22:57] I might have been the first person in the mw-core team to have the (WMF) on my account [21:23:11] and since I never needed that and never had that staff wiki flag [21:23:27] I also never needed my WMF account that was later made for me by others [21:24:51] I'm going to actually make a task proposing the WMDE suffix blocking on wikitech and send it by Lessig and others for feedback. [21:31:07] wikitech/developer accounts are supposed to be exempt from the (WMF) policy [21:31:40] but I think people just went along with it to have consistent usernames and because they saw others do it and ... definitely agreed that it's all a problem of our own creation [21:32:20] people usually like to err on the side of caution "just in case" and they see others doing it they think it is mandatory now [21:33:26] similarly sometimes tickets get custom policy or NDA when they could actually be public but people werent sure enough