[10:47:21] !log tools.notwikilambda configured $wgFooterIcons if notwikilambda-configure-wgFooterIcons URL parameter isn’t set to false, working around T291325 [10:47:25] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.notwikilambda/SAL [13:49:34] !log tools.lexeme-forms deployed 3c1b6e0810 (readinessProbe → startupProbe to avoid bloating access log); deployed by adding readinessProbe: null to the patch file and patching the deployment with that [13:49:38] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.lexeme-forms/SAL [15:34:51] !log tools.notwikilambda improved automatic updates of function orchestrator and evaluator, should work without downtime now [15:34:57] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.notwikilambda/SAL [15:48:58] !log tools.notwikilambda temporarily disabled SyntaxHighlight extension due to issues with the Pygments server [15:49:04] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.notwikilambda/SAL [16:39:12] !log tools.notwikilambda rolled back SyntaxHighlight_GeSHi to commit 580ce3425f, because I2e82e5aa2a is incompatible with pygments-server (provides input as file instead of stdin) [16:39:15] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.notwikilambda/SAL [16:39:32] !log tools.notwikilambda (and reenabled SyntaxHighlight_GeSHi) [16:39:38] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.notwikilambda/SAL [16:47:40] !log tools.notwikilambda changed restart cronjob to 9:30 and 21:30 to avoid congestion at midnight/noon [16:47:43] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.notwikilambda/SAL [17:23:07] lucaswerkmeister: how does your pygments-server code work? [17:23:31] sends the command line arguments and stdin to a flask server [17:23:36] the fake pygmentize is here https://github.com/lucaswerkmeister/pygments-server/blob/main/pygmentize [17:24:25] and then the main part of the server is just this bit https://github.com/lucaswerkmeister/pygments-server/blob/451d6c93901b0dda96fc9de0681dbc781df44c80/app.py#L46-L53 [17:24:52] fake stdin, fake stdout, run pygments.cmdline.main(), return fake stdout (so flask will send it back to curl) [17:25:02] hm [17:26:26] is my understanding correct that, in production, pygments is eventually going to run in a container that has both PHP (for the shellbox server) and Python (for pygments itself)? [17:26:41] yes [17:26:44] ok [17:27:03] there's also https://phabricator.wikimedia.org/T257988 [17:27:29] ah, I wasn’t aware of that [17:27:47] but I was aware of the Khan server itself, it didn’t quite work for me [17:27:52] that’s why I wrote my own [17:28:05] maybe I should at least comment that on the task, probably useful information in general [17:29:12] now that I separated out all the pygmentize calls, I think it should be straightforward to add in a class that delegates everything to a HTTP server [17:29:16] otherwise – I’m okay with just keeping SyntaxHighlight frozen at the old version for the notwikilambda wiki, it’s probably going to be deleted in less than a year anyways (once Wikifunctions launches) [17:29:28] hm, or that [17:29:50] if we can agree on a protocol ^^ [17:30:38] hopefully should be as simple as /css /lexers /highlight