[15:15:09] Is Wikipedia's Parsoid endpoint locally accessible within Wikimedia Cloud Services, i.e. without needing to leave the local Wikimedia production network? [15:20:59] @harej Pedantically no, because the WMCS tenant network is outside of the prod environment, but functionally yes the traffic never leaves WMF owned and managed equipment. [15:22:53] There is increased appetite to replace InternetArchiveBot's home-grown, untested parser with Parsoid. We were recommended to use the foundation-maintained endpoint rather than run our own, but then we would run into I/O bottlenecks. But if it's local to the network, I don't think those kinds of bottlenecks would exist in any meaningful way. Does that sound right? [15:28:19] @harej a network call is going to have more latency than local code execution, but I can't say if that will become a bottleneck in the iabot process or not. If it would mean hundreds of thousands of new requests to Parsoid per unit time y'all should probably have some conversations with the parsing and SRE teams before going all in on a refactor. [15:29:18] but any home grown wikitext parser is guaranteed to miss edge cases [18:24:31] !log toolsbeta rolling out kubernetes patch release 1.18.20, cluster is currently at 1.18.18 [18:24:33] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Toolsbeta/SAL [19:37:28] !log tools.lexeme-forms deployed c88b1962fa (Igbo nouns) [19:37:31] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.lexeme-forms/SAL