[01:47:27] I am trying to add a sk-ssh-ed25519@openssh.com ssh-key to [[User:XtexChooser]]. [01:47:47] but it says that the key is "wrong or in incorrect format" [02:03:41] xtex[m], unfortunately not all the various WMCS systems that use SSH keys support sk-* keys yet [02:04:16] ops, thx [02:07:08] actually, it looks like it's production servers, not wmcs :) [02:08:27] there's no tracking task for -sk keys specifically, but there are some notes in https://phabricator.wikimedia.org/T337037 [10:19:16] !log tools deploy toolforge-cli 0.3.2 [10:19:18] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [12:22:52] I requested to increase Toolforge quota via Phab T340716. How long does it usually take to process? [12:22:52] T340716: Request increased quota for hoiscript Toolforge tool - https://phabricator.wikimedia.org/T340716 [12:25:35] More than 4 hours ;) [12:26:08] As per https://phabricator.wikimedia.org/project/view/4834/ [12:26:16] >Requests can be granted anytime by the WMCS clinic duty team member when having a +1 from any other team member, feel free to ping us on irc if your request is urgent. [12:26:16] >For bigger quota requests, a discussion and agreement within the Cloud Services team will happen during the team meeting every Wednesday (08:00 PST). This schedule may be effected by holidays, conferences, or other unavailability. [12:33:32] Reedy: Thanks. I overlooked the tip. [12:33:35] But why 4 hours, instead of being not longer or shorter? [12:34:35] I was meaning 4 hours is about how long since you filed the request [12:52:53] !log tools.slumpartikel Restarting webservice with the kubernetes backend and the php7.4 webservice [12:52:55] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.slumpartikel/SAL [13:52:52] !log paws T340698 OpenRefine version bump [13:52:56] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Paws/SAL [13:52:56] T340698: New upstream release for OpenRefine - https://phabricator.wikimedia.org/T340698 [14:54:51] xtex[m]: AntiComposite: the bastions are on bullseye so you should be able to use an -sk key to log in to any bullseye or bookworm instances.. you might be able to get around that error (which I assume is because the wikitech hosts are still on buster) by using https://toolsadmin.wikimedia.org/profile/settings/ssh-keys/ to add keys instead [15:05:15] Does Cirrussearch support insource search by regex? The page https://wikitech.wikimedia.org/wiki/Help:CirrusSearch_elasticsearch_replicas does not provide useful information [15:09:11] Yetkin: yes it does, please see https://www.mediawiki.org/wiki/Help:CirrusSearch#Insource (if it's for a non WMF wiki setup you will have to install the elasticsearch wikimedia/extra plugin, search for wgCirrusSearchWikimediaExtraPlugin in docs/settings.txt) [15:17:39] No, the problem is that my insource search (on wiki) times out with complex regular expressions. Is there any way to make the search off wiki (via cloud or API)? [15:20:04] Yetkin oh ok, I suspect that cloudelastic is going to be slower than WMF production wiki, one way to help a insource:// is to narrow the search space with other keywords (i.e. can you narrow it down with additional hastemplate:XYZ or the like) [15:24:16] But if you want to experiment with shipping insource:// queries to cloudelastic you will have to construct the raw elastic query yourself, one way is to see what CirrusSearch generates, you can append '&cirrusDumpQuery' to you Special:Search URL, e.g. [15:24:18] https://www.mediawiki.org/w/index.php?search=insource%3A%2Fmyregex+expression%2F&title=Special%3ASearch&ns0=1&ns12=1&ns100=1&ns102=1&ns104=1&ns106=1&cirrusDumpQuery [15:31:44] thanks for the info. Where to put this JSON to search? [15:35:10] Yetkin sadly this not obvious you will have to run this from your own toolsforge or cloudvps (https://wikitech.wikimedia.org/wiki/Help:Cloud_Services_introduction) [15:36:58] https://github.com/wikimedia/tools-global-search is one example app running in toolsforge that queries cloudelastic [15:42:35] hmm, interesting. It looks like insource does not support the regex "(\s)?" [15:46:54] Yetkin yes CirrusSearch relies on the lucene regex engine that does not support all the features you usually see from a PCRE engine (i.e. https://www.elastic.co/guide/en/elasticsearch/reference/current/regexp-syntax.html) [15:47:54] handy character classes like \s are not supported, you have to be explicit with those using [abc] [15:50:23] I would like to match spaces, actually [16:01:42] Yetkin sadly you will have to be explicit on the spaces you want to search for and add them all to an explicit [] character class, e.g. [ ] (not obvious) but searches for usual spaces and non breaking spaces, if you don't care about fancy space chars simply search for a simple space [16:25:46] yes, I can search for the space character but I would like to it be dynamic (zero or more spaces)