[07:27:35] Crazy that people use this skin when it's borked every other day [07:50:29] it's borked every other day bc it's actively maintained [07:52:18] Surely one of the key jobs of a maintainer is to make sure that when they push patches those patches actually work. [08:40:06] I'm pretty sure this time it's only borked because people can't figure out how to update it properly when it changes more than some css styling [08:58:30] It won't be borked unless you update it the exact same way as Star Citizen Tools. Every breaking change requires moving to an exact commit unless you purge the parser cache every time. [09:00:06] At least upstream recognizes that this is an issue and ships a compat flag now: https://github.com/StarCitizenTools/mediawiki-skins-Citizen/commit/e53016721750ef2224ced590a8066a6777df4d36#diff-936180ff1d27c7de3e0601e9d558986a307b662d5886bd5d25539270b490bfeaR6. So in theory no one has to suffer in future upgrades. [11:00:28] I mean I assume those patches work on alistair's machine [11:00:58] but we couldn't realistically purge the parser cache of every page on every wiki using citizen as default skin [11:01:24] whereas if you're just in charge of a single wiki that's much less of a problem [16:58:57] The HTML to CSS/JS mismatch is a known limitation with ResourceLoader that affects all skins and extensions. For example, Vector 2022 updates that contain HTML change span multiple days because of the same parser cache reason. And they deploy continuously [17:03:40] We also dogfood the latest commit on Star Citizen Wiki most of the time too for live testing [17:04:22] Yeah usually it'll self-heal after the parser cache expire [17:13:45] Yeah it has less breakage for us because we update continuously and have a shorter parser cache expiry. If it's bad enough then we just bump the cache epoch to purge the parser cache [17:15:19] Either way I think @posix_memalign took the most reasonable approach here [23:08:43] by "alistair's machine" I meant the star citizen wiki, which now that I think about it was horrifically unclear lmao