[08:51:26] <wikibugs>	 10serviceops, 10SRE, 10Wikimedia-production-error: PHP7 corruption reports in 2020-2021 (Call on wrong object, etc.) - https://phabricator.wikimedia.org/T245183 (10Ladsgroup) This sounds like that was another case in mw1331: https://logstash.wikimedia.org/goto/07c52e2c90e05449eb7acc4df15c0cb5
[09:23:55] <wikibugs>	 10serviceops, 10MW-on-K8s, 10SRE, 10Release-Engineering-Team (Radar): The restricted/mediawiki-webserver image should include skins and resources - https://phabricator.wikimedia.org/T285232 (10Joe)
[15:30:51] <bd808>	 _joe_: what is your recommendation for a nodejs compile image to replace nodejs10-devel? Is there something actively used that you feel is less fragile?
[15:31:11] <_joe_>	 bd808: no, we need to create it for you
[15:31:13] <_joe_>	 :)
[15:31:56] <_joe_>	 bd808: let me talk with moritzm, but I feel we should offer a later version of nodejs on buster
[15:32:31] <_joe_>	 the image by itself wasn't fragile, it was built when a bug was present, and, once the bug was removed, it caused a bug in it
[15:32:37] <bd808>	 there is https://phabricator.wikimedia.org/T284346 asking for nodejs12 in backlog
[15:33:13] <bd808>	 tracking debian for nodejs bits does feel like a recipe for complaining devs
[15:33:35] <_joe_>	 yeah let's not do that, I think I commented so in the task
[15:33:59] <_joe_>	 more specifically, if you have two images named nodejs10-devel, they should both include the same nodejs version
[23:45:22] <wikibugs>	 10serviceops, 10MediaWiki-Parser, 10SRE, 10Performance-Team (Radar): purgeParserCache.php: Cannot purge this kind of parser cache - https://phabricator.wikimedia.org/T250231 (10Krinkle)