[02:01:01] <MirahezeRelay>	 <mr.shirokuma> [1/6] Hi! It seems like images from Wikimedia Commons are not displaying across multiple Miraheze wikis, not just mine.
[02:01:02] <MirahezeRelay>	 <mr.shirokuma> [2/6] Details:
[02:01:02] <MirahezeRelay>	 <mr.shirokuma> [3/6] Images from Commons are broken or appearing as empty spaces.
[02:01:02] <MirahezeRelay>	 <mr.shirokuma> [4/6] I confirmed this issue on other Miraheze wikis as well.
[02:01:03] <MirahezeRelay>	 <mr.shirokuma> [5/6] I've tried purging the pages, but it didn't resolve the issue.
[02:01:03] <MirahezeRelay>	 <mr.shirokuma> [6/6] Is there a known issue with InstantCommons or the thumbnail server right now? Thanks!
[02:03:32] <MirahezeRelay>	 <pskyechology, replying to mr.shirokuma> https://discord.com/channels/407504499280707585/407537962553966603/1469860034438496368
[02:04:18] <MirahezeRelay>	 <mr.shirokuma> Thanks
[04:35:51] <MirahezeRelay>	 <cosmicalpha> We may be to push up the 1.45 upgrade to sometime next week even now. I havent seen any issues at withh during upgrade or it fataling after. Once we remove totally broken extensions and finish testing the rest we can probably be ready for upgrading everything.
[05:05:00] <MirahezeRelay>	 <pixldev, replying to cosmicalpha> Famous last words
[11:07:52] <MirahezeRelay>	 <posix_memalign> [1/3] I looked into [Pppery's Flow export script](https://gitlab.wikimedia.org/pppery/flow-export-with-history) which was used to convert mediawiki.org Flow discussions to wikitext in [T377051](https://phabricator.wikimedia.org/T377051), and it's not going to be easy to do the same on MH. 
[11:07:53] <MirahezeRelay>	 <posix_memalign> [2/3] I found 2 issues so far. First, it relies on a database connection, which is possible on [PAWS](https://wikitech.wikimedia.org/wiki/PAWS) but harder to replicate on MH infrastructure. Second, it uses the [Wikimedia REST API](https://www.mediawiki.org/wiki/Wikimedia_REST_API) which is  "Available for Wikimedia projects only" (e.g. https://www.mediawiki.org/api/rest_v1/transform
[11:07:53] <MirahezeRelay>	 <posix_memalign> [3/3] /html/to/wikitext).
[11:22:04] <MirahezeRelay>	 <posix_memalign> The database issue can possibly be resolved if we allow the bot to connect to prod servers through mwtask, but the REST API thing is harder. I suppose we can build a simple conversion script with PHP which emulates the API by calling Parsoid to convert HTML to wikitext.
[11:27:09] <MirahezeRelay>	 <posix_memalign> If we don't want the full edit history, it'll make our lives a lot easier because we can just use `convertToText.php` to convert Flow boards to wikitext and then replace them.
[12:31:26] <MirahezeRelay>	 <abaddriverlol> Isn't there a html2wt endpoint in the MediaWiki Rest API as well?
[12:33:26] <MirahezeRelay>	 <abaddriverlol> I think it's `/v1/transform/html/to/wikitext`
[12:33:43] <MirahezeRelay>	 <abaddriverlol> per <https://en.wikipedia.org/w/index.php?api=mw-extra&title=Special%3ARestSandbox#/default/post_v1_transform_html_to_wikitext>
[14:19:12] <MirahezeRelay>	 <blankeclair, replying to abaddriverlol> yeah, the rainverse wiki calls it internally
[14:20:05] <MirahezeRelay>	 <blankeclair> https://rainverse.wiki/wiki/Module:SpeciallyCursed/AutoPageCreator/Comicfury#L-40
[14:37:57] <MirahezeRelay>	 <originalauthority> (if you're feeling risky you can also call the VE endpoint to parse wt -> html ig)
[14:38:11] <MirahezeRelay>	 <originalauthority> That probably has some unintended side effects though by removing stuff VE can't handle 🙁
[17:10:41] <MirahezeRelay>	 <malcolmtuckershop> Hiya been having issues on the TFR wiki related to this issue https://issue-tracker.miraheze.org/T14793, im wondering if there are any things that can be done to help mitigate this issue in the meantime while its being looked at?
[17:30:58] <MirahezeRelay>	 <notaracham> It remains under active investigation, it's proving to be quite the issue.
[18:15:18] <MirahezeRelay>	 <notaracham, replying to malcolmtuckershop> To expand on that answer a bit, you can try purging pages with redlinked files, but it will be hit or miss if that works and it may happen again while the issue remains active.
[18:15:31] <MirahezeRelay>	 <malcolmtuckershop, replying to notaracham> ok thank you :)
[22:42:15] <MirahezeRelay>	 <paladox, replying to malcolmtuckershop> this should have been resolved
[22:50:18] <MirahezeRelay>	 <thewwrnerdguy> [1/8] uhhh
[22:50:18] <MirahezeRelay>	 <thewwrnerdguy> [2/8] I was trying to reply to https://issue-tracker.miraheze.org/T14911 to say the page was working fine for me, my exact message was ```
[22:50:19] <MirahezeRelay>	 <thewwrnerdguy> [3/8] hmm it's working fine for me```
[22:50:19] <MirahezeRelay>	 <thewwrnerdguy> [4/8] transcript of image:
[22:50:19] <MirahezeRelay>	 <thewwrnerdguy> [5/8] ```
[22:50:20] <MirahezeRelay>	 <thewwrnerdguy> [6/8] Unhandled Exception ("Exception")
[22:50:20] <MirahezeRelay>	 <thewwrnerdguy> [7/8] Subscriber transactions must be existing PHIDs or usernames (found key "0" on transaction of type "core:subscribers").```
[22:50:20] <MirahezeRelay>	 <thewwrnerdguy> [8/8] https://cdn.discordapp.com/attachments/1006789349498699827/1470190031497986058/image.png?ex=698a64aa&is=6989132a&hm=9ae2b5d0447f01104570438b905ff1a63a7d93499b2d6e8242d2651b76bc88e6&
[22:50:53] <MirahezeRelay>	 <thewwrnerdguy> same thing happens if I try to press "Subscribe"
[22:51:14] <MirahezeRelay>	 <pskyechology> @paladox appears to be a post-upgrade bug? ^
[22:51:39] <MirahezeRelay>	 <paladox> hmm
[22:58:01] <MirahezeRelay>	 <paladox> Seems https://github.com/phorgeit/phorge/commit/babeed68715c2b48c6f80cfe1217e8c474349d38 break it
[22:58:07] <MirahezeRelay>	 <paladox> so i checked out the parent which fixed it
[23:10:29] <MirahezeRelay>	 <posix_memalign, replying to abaddriverlol> Oh that's nice to know. Thanks! The only obstacle would be the DB connection then.
[23:12:42] <MirahezeRelay>	 <abaddriverlol> What does it use the db connection for?
[23:13:08] <MirahezeRelay>	 <posix_memalign> [1/2] In the mean time I experimented with a maintenance script to delete flow boards and replace them with wikitext pages. This is a rough draft with more LLM meddling than I'm comfortable with, so we definitely want to read it carefully. But, if we go this route it should be easier to work with since it's just 175 lines of PHP.
[23:13:08] <MirahezeRelay>	 <posix_memalign> [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1470195776184389827/message.txt?ex=698a6a03&is=69891883&hm=0798d3e14ba6fa4e4c99459727dd3f3ebb3250fe1e24058e495a31779c090ba5&
[23:13:49] <MirahezeRelay>	 <posix_memalign, replying to abaddriverlol> IIRC to find all the flow boards. Flow has no API for that, so the alternative is to go through every single page listing their content model and find the ones with content model `flow-board`.
[23:14:16] <MirahezeRelay>	 <posix_memalign, replying to posix_memalign> This script works on simple localhost test cases but I haven't run it on beta or prod yet (for obvious reasons).
[23:21:38] <MirahezeRelay>	 <posix_memalign, replying to posix_memalign> I think the script does more than that (in `getSignature` and `addNullRevisions`. The "listing all flow boards" issue was the first one I encountered with the API, but it seems that there are more things which are more convenient with SQL.
[23:37:44] <MirahezeRelay>	 <posix_memalign> [1/3] @cosmicalpha Looks like ProtectSite does work to some extent. When I try to create a page with an alt, I get a database exception. 
[23:37:44] <MirahezeRelay>	 <posix_memalign> [2/3] Very odd that the behavior is different from beta though. 
[23:37:45] <MirahezeRelay>	 <posix_memalign> [3/3] https://logging.wikitide.net/messages/graylog_1011/6bfbcdf4-0546-11f1-b446-bc2411bdcdc1
[23:44:35] <MirahezeRelay>	 <posix_memalign> [1/2] 3D's behavior is different from beta as well. On beta it doesn't show any preview. On PTW it's stuck on "Loading thumbnail".
[23:44:36] <MirahezeRelay>	 <posix_memalign> [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1470203692824137840/image.png?ex=698a7163&is=69891fe3&hm=7b31c6d1422ab616b8cbbd89fb9964d6f8240637e6a050c0f4fdc008421ff5b8&