Wikitech-l February 2024

wikitech-l@lists.wikimedia.org

29 participants
32 discussions

[Train] 1.42.0-wmf.19 / wmf.20 status: blocked on T336504 (Transcluding Special:Prefixindex forces default skin), may require Monday rollback
by Brennen Bearnes 26 Feb '24

26 Feb '24

This week's 1.42.0-wmf.20 version of MediaWiki is blocked[0], and 1.42.0-wmf.19 may require a Monday rollback, which is a situation we hope to avoid. We can't proceed until the following issue is resolved: * T336504 - Transcluding Special:Prefixindex can force the default skin - https://phabricator.wikimedia.org/T336504 For context, see the Village pump discussion linked here: * https://phabricator.wikimedia.org/T336504#9572477 Once this issue is resolved, the train can proceed normally for the week. Thank you for any help! -- Your designated sacrificial train victims [0]. https://phabricator.wikimedia.org/T354438

1 0

Northward Datacentre Switchover (March 2024)
by effie mouzeli 26 Feb '24

26 Feb '24

Dear all, *"There is nothing permanent except change - Heraclitus"* On *Wednesday March 20th 2024,* the SRE team will run a planned datacentre switchover, moving all wikis from *codfw* to *eqiad*. This is an important periodic test of our tools and procedures, to ensure the wikis will continue to be available even in the event of major technical issues in our primary home. It also gives all our SRE and ops teams a chance to do maintenance and upgrades on systems in codfw that normally run 24 hours a day. The switchover process requires a brief read-only period for all Foundation-hosted wikis, which will start on *Wednesday March 20th 2024 @ 14:00 UTC*, and will last for just a few minutes while we execute the migration as efficiently as possible. All our public and private wikis will be continuously available for reading, as usual, but editing will be unavailable during the process. Users will see a notification of the upcoming maintenance, and anyone still editing will be asked to try again in a few minutes. CommRel will soon begin notifying communities of the read-only window. If you like, you can follow along on the day in the public *#wikimedia-operations* channel on IRC. To report any issues, you can reach us in *#wikimedia-sre* on IRC, or file a Phabricator ticket <https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?projects=Data…>with the #datacenter-switchover tag; we'll be monitoring closely for reports of trouble during and after the switchover. The switchover and its preparation will be tracked under https://phabricator.wikimedia.org/T357547. On behalf of the SRE team, please excuse the disruption, and we would like to thank everyone in various departments who are involved in planning this work. If you have any questions, please reply directly to this email. Kind Regards, -effie

2 1

Etherpad maintenance 2024-02-26 09:00 - 10:00 UTC
by Jelto Wodstrcil 26 Feb '24

26 Feb '24

Hi all, we have to do *maintenance* on etherpad.wikimedia.org next *Monday, 2024-02-26** 09:00 UTC*. The maintenance involves the switch of the underlying hardware and a version upgrade. So the estimated downtime is around *60 minutes*. If you are working on a document currently please make a backup outside of Etherpad and do not use Etherpad during the maintenance window. I'll let you know when the maintenance is finished. You can find more information in https://phabricator.wikimedia.org/T316421. Greetings jelto

1 1

23 Feb '24

Hello all, The next language community meeting is coming up in a few weeks - *February 21st, 12:00 pm UTC*. If you're interested, you can sign up on this wiki page: < https://www.mediawiki.org/w/index.php?title=Wikimedia_Language_engineering/… >. This meeting is for individuals involved in creating content or managing technical aspects across different language communities. This will be a participant-driven meeting, where we collectively discuss specific technical issues related to language wikis and work together to find possible solutions. This could involve anything from fixing a broken template on the Kurdish wiki to brainstorming ideas for growing content on the Tulu Wiktionary, currently in the Wikimedia Incubator, or celebrating the creation of Fon Wikipedia, to using MinT for content translation. Feel free to add any *technical updates* related to your project or ideas for *problem-solving* discussion that you would like to share during the meeting to the notes document here: < https://etherpad.wikimedia.org/p/language-community-meeting-february-2024>. If you need interpretation support from English to another language, please let us know by sending an email to ssethi(a)wikimedia.org. Looking forward to your participation! Cheers, Jon, Mary & Srishti *Srishti Sethi* Senior Developer Advocate Wikimedia Foundation <https://wikimediafoundation.org/>

2 4

APIi page generator namespace order
by Bináris 22 Feb '24

22 Feb '24

Hi, I query special pages through API (concretely Special:UnconnectedPages), and I noticed that main namespace articles are yielded first. It seems that pages are ordered by namespace numbers. Is it a guaranteed behaviour? (If so, I can break from the loop at te first page not in 0 namespace which would be nice.) -- Bináris

2 2

Parsoid Read Views is enabled for DiscussionTools in Wikitech
by Mateus Santos 22 Feb '24

22 Feb '24

Hello everyone, I am glad to inform you that as part of our initial experimentations with Parsoid Read Views, Parsoid is turned on as the default read views renderer in Wikitech for DiscussionTools. Here's the rationale <https://www.mediawiki.org/wiki/Parsoid/Parser_Unification/Confidence_Framew…> behind our confidence to roll-out this experimental feature and collect feedback. This is an opportunity to experiment the changes confidently before we start rolling out more wikis. If this disrupts your workflow, don’t worry you can still opt out through a user preference or turn Parsoid off on the page you’re navigating in the Tools submenu. To report bugs and issues, please look at our known issues <https://www.mediawiki.org/wiki/Parsoid/Parser_Unification/Known_Issues> documentation and if you found a new bug please create a phab ticket and tag the Content Transform Team in Phabricator <https://phabricator.wikimedia.org/project/view/5846> or send us a message in our slack channel #content-transform-team. More relevant info about our roll-out strategy can be found on this wiki page <https://m.mediawiki.org/wiki/Parsoid/Parser_Unification/Confidence_Framework> . Best regards, Mateus

1 0

About problematic Chinese language variant support on mobile apps
by psnbaotg 22 Feb '24

22 Feb '24

Hi all, Today when playing around Wikipedia iOS app I'm surprised to find out that the Chinese language variant support is still somewhat broken. There is no zh-cn variant available, only zh-hans (displayed as "Simplified Chinese"). I haven't touched the Android app for a while, but in my last review it mistakenly includes zh-hans and zh-hant variants. As I mentioned in https://phabricator.wikimedia.org/T305319, the correct list of variants the app should include should be: zh-cn, zh-sg, zh-my, zh-tw, zh-mo, zh-hk. Other zh variants have incomplete conversion, thus should be excluded. I hope somebody at the relevant team could reach out to me and discuss possible solutions. If you don't understand the reason to do this I can give a detailed explanation. I believe this task should not be triaged as "Low" because it has negative impacts on Chinese readers. Best regards, Diskdance

2 5

Parsoid template transclusion behavior
by psnbaotg 18 Feb '24

18 Feb '24

Hello, Recently I'm researching Parsoid's design as MW is migrating to Parsoid. I found out that due to its single-pass tokenizing design, templates are not handled textually as the legacy parser does. This is good as the HTML now have information about which template they are transcluded from. However, https://www.mediawiki.org/wiki/Parsoid/limitations says "We have since decided to use the PHP preprocessor for template expansions, which side-steps these issues by reverting to the traditional textual preprocessor pass". Is this still true now? Best regards, Diskdance

2 1

OOUI v0.49.0 released
by atomasevich＠wikimedia.org 17 Feb '24

17 Feb '24

Hi all, OOUI v0.49.0 was released yesterday. It will be rolled out in MediaWiki via the deployment train starting on Tuesday, 13 February 2024. There are several breaking changes in this release. Please check your code carefully and make the suggested updates as necessary. - SearchInputWidget, TextInputWidget: getSaneType() has been changed to getValidType() to reflect more inclusive language. Please check your code to make sure you're using the updated method name. - SelectWidget: getItemMatcher() no longer supports the value of `true` for the mode argument, which has been deprecated since v0.30.4. Use `'exact'` instead. - WindowManager: The alias toggleAriaIsolation(), deprecated since v0.44.1, has been removed. Use toggleIsolation() instead. Other changes include: - JavaScript documentation has been migrated from JSDuck to JSDoc3. - The Less variable @line-height-base, deprecated since v0.42.0, has been removed. Use @line-height-label instead. You can find a full list of changes in the changelog[1]. As always, interactive demos[2] and code-level documentation[3] are available on doc.wikimedia.org, along with library documentation[4] on mediawiki.org. [1] - https://gerrit.wikimedia.org/g/oojs/ui/+/v0.49.0/History.md [2] - https://doc.wikimedia.org/oojs-ui/master/demos/#widgets-mediawiki-vector-ltr [3] - https://doc.wikimedia.org/oojs-ui/master/js [4] - https://www.mediawiki.org/wiki/OOUI Happy UI-ing,Anne -- Anne Tomasevich (she/her) Staff Software Engineer, Design System Wikimedia Foundation

2 1

Where to find information about images in the Docker registry
by Sebastian Berlin 16 Feb '24

16 Feb '24

I'm updating some blubberised repos that a colleague of mine created some time ago and I'm not sure what base images from the Docker registry <https://docker-registry.wikimedia.org/> are the best to use. For instance, one repo uses docker-registry.wikimedia.org/wikimedia-buster as base image in .pipeline/blubber.yaml. I thought I'd update to Bookworm as the newest stable Debian release, but there is no image "wikimedia-bookworm", only "bookworm". I'd like to know what's different in the the ones with the wikimedia- prefix. There are also several different ones for Python, e.g. "python3", "python3-buster" and "python3-build-buster". Is there documentation somewhere or links to repos where I can see what Docker or Blubber files were used to create them? *Sebastian Berlin* Utvecklare/*Developer* Wikimedia Sverige (WMSE) E-post/*E-Mail*: sebastian.berlin(a)wikimedia.se Telefon/*Phone*: (+46) 0707 - 92 03 84

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l February 2024