Wikitech-l

wikitech-l@lists.wikimedia.org

25 participants
23118 discussions

Gerrit upgrade Monday June 10th at 8am UTC
by Antoine Musso 06 Jun '24

06 Jun '24

Hello, I cancelled the Gerrit 3.9 upgrade I originally scheduled on Monday. I am rescheduling it for *Monday June 10th at 8am UTC*. It is immediately after the UTC morning backport & config window. The upgrade requires the Gerrit service to be stopped for the duration of the upgrade. Given we do not need to reindex all the changes, the downtime should be just a few minutes. Gerrit 3.9 brings: * Support for diff3 rendering for changes having conflict markers (T359821 <https://phabricator.wikimedia.org/T359821>) which corresponds to cgit merge.conflictStyle=diff3. * User Suggested Edits <http://gerrit-documentation.storage.googleapis.com/Documentation/3.9.5/user…>, an easy way for reviewers to suggest code changes which can be easily applied by the change owner. One can imagine CI would be able to offers suggestions as well (such as phpcb from PHP CodeSniffer or eslint?). * Gerrit would now use "Revert^2" syntax when crafting a revert instead of chaining them as "Revert "Revert "Revert...". * And more UI changes <https://www.gerritcodereview.com/3.9.html#gerrit-ui-changes> The release notes: https://www.gerritcodereview.com/3.9.html <https://www.gerritcodereview.com/3.9.html>The upgrade task: https://phabricator.wikimedia.org/T354887 Deployment calendar entry <https://wikitech.wikimedia.org/wiki/Deployments#deploycal-item-20240610T0800> Antoine "hashar" Musso

1 0

Talk to the Search Platform / Query Service Team—June 8, 2024
by Guillaume Lederrey 05 Jun '24

05 Jun '24

Hello all! The Search Platform Team usually holds an open meeting on the first Wednesday of each month. Come talk to us about anything related to Wikimedia search, Wikidata Query Service (WDQS), Wikimedia Commons Query Service (WCQS), etc.! Feel free to add your items to the Etherpad Agenda for the next meeting. Details for our next meeting: Date: Wednesday, June 5, 2024 Time: 15:00-16:00 UTC / 08:00 PDT / 11:00 EDT / 17:00 CEST Etherpad: https://etherpad.wikimedia.org/p/Search_Platform_Office_Hours Google Meet link: https://meet.google.com/vgj-bbeb-uyi Join by phone: https://tel.meet/vgj-bbeb-uyi?pin=8118110806927 Have fun and see you soon! Guillaume -- *Guillaume Lederrey* (he/him) Engineering Manager Wikimedia Foundation <https://wikimediafoundation.org/>

1 2

Phabricator: Proposal not to automatically copy subscribers and projects when creating a subtask
by Andre Klapper 05 Jun '24

05 Jun '24

Hello dear satisfied Phabricator users, https://phabricator.wikimedia.org/T239378 is a proposal to stop automatically copying all Subscribers and Project Tags from a parent task when creating a subtask in Phabricator. Such a change likely would help reduce notification overload[1] for many folks, in the frequent cases when a large/epic task is broken down into dozens of smaller, more detailed subtasks. If you have any concerns about this proposal, please first read all comments in T239378 and then comment yourself. You are also welcome to add a thumb pointing into your favorite vertical direction by using "Award Token" in the sidebar. Thanks a lot!, andre [1] https://www.mediawiki.org/wiki/Phabricator/Help/Managing_mail -- Andre Klapper (he/him) | Bugwrangler https://blogs.gnome.org/aklapper/

1 0

Announcing Scholarship Applications for the Wikimedia Technology Summit (WTS-2024) - October at Hyderabad
by Kaśyap కశ్యప్ 03 Jun '24

03 Jun '24

Dear Wikimedians, We are pleased to announce that the scholarship application for the Wikimedia Technology Summit (WTS) 2024 <https://meta.wikimedia.org/wiki/3rd_Wikimedia_Technology_Summit_(WTS_2024)> is now open! We invite all Indic Wiki project Tech contributors, active Wikimedians in WikiTech, and open-source volunteers to apply for a scholarship to attend the summit, which will be held at IIIT Hyderabad, India <https://www.iiit.ac.in/>, in October 2024. Wikimedians residing in India are encouraged to apply for this opportunity to join us at WTS 2024. You can find more details about the scholarships, including eligibility criteria and the application process, more details here <https://meta.wikimedia.org/wiki/3rd_Wikimedia_Technology_Summit_(WTS_2024)> To apply for a scholarship, please fill out the application form at https://forms.gle/a9xZjwfbU1VzNghg7 The deadline for submissions is July 10, and applicants will be informed of the decisions in July 2024. We look forward to receiving your applications and hope to see you at WTS 2024! Best regards, Kasyap wts.indicwiki(a)iiit.ac.in On behalf of the WTS 2024 Scholarship Committee

1 0

Gerrit upgrade Monday June 3rd at 8am UTC
by Antoine Musso 03 Jun '24

03 Jun '24

Hello, I will be *upgrading Gerrit* from the 3.8 series to the 3.9 series. I have scheduled the upgrade for *Monday June 3rd at 8am UTC*. It is immediately after the UTC morning backport & config window. The upgrade requires the Gerrit service to be stopped for the duration of the upgrade. Given we do not need to reindex all the changes, the downtime should be just a few minutes. Gerrit 3.9 brings: * Support for diff3 rendering for changes having conflict markers (T359821 <https://phabricator.wikimedia.org/T359821>) which corresponds to cgit merge.conflictStyle=diff3. * User Suggested Edits <http://gerrit-documentation.storage.googleapis.com/Documentation/3.9.5/user…>, an easy way for reviewers to suggest code changes which can be easily applied by the change owner. One can imagine CI would be able to offers suggestions as well (such as phpcb from PHP CodeSniffer or eslint?). * Gerrit would now use "Revert^2" syntax when crafting a revert instead of chaining them as "Revert "Revert "Revert...". * And more UI changes <https://www.gerritcodereview.com/3.9.html#gerrit-ui-changes> The release notes: https://www.gerritcodereview.com/3.9.html <https://www.gerritcodereview.com/3.9.html>The upgrade task: https://phabricator.wikimedia.org/T354887 Deployment calendar entry <https://wikitech.wikimedia.org/wiki/Deployments#deploycal-item-20240603T0800> Antoine "hashar" Musso Wikimedia Release Engineering

3 3

SQL problem
by Martin Domdey 01 Jun '24

01 Jun '24

Hi, I want to look in table comment column comment-text for %Unsinn% case-insensitive with this clause: where comment_text collate utf8mb4_general_ci like '%Unsinn%'; but this gives me error: COLLATION 'utf8mb4_general_ci' is not valid for CHARACTER SET 'binary' How can I proceed such a collation? Kind regards Doc Taxon ...

3 4

Phabricator monthly statistics - 2024-05
by aklapper＠wikimedia.org 01 Jun '24

01 Jun '24

Hi Community Metrics team, This is your automatic monthly Phabricator statistics mail. Accounts created in (2024-05): 329 Active Maniphest users (any activity) in (2024-05): 1196 Task authors in (2024-05): 601 Users who have closed tasks in (2024-05): 322 Projects which had at least one task moved from one column to another on their workboard in (2024-05): 325 Tasks created in (2024-05): 2517 Tasks closed in (2024-05): 2732 Open and stalled tasks in total: 53662 * Only open tasks in total: 52658 * Only stalled tasks in total: 1004 Median age in days of open tasks by priority: Unbreak now: 3 Needs Triage: 1010 High: 1197 Normal: 2080 Low: 2606 Lowest: 3086 (How long tasks have been open, not how long they have had that priority) To see the names of the most active task authors: * Go to https://wikimedia.biterg.io/ * Choose "Phabricator > Overview" from the top bar * Adjust the time frame in the upper right corner to your needs * See the author names in the "Submitters" panel TODO: Numbers which refer to closed tasks might not be correct, as described in https://phabricator.wikimedia.org/T1003 . Yours sincerely, Fab Rick Aytor (via community_metrics.sh on phab1004 at Sat 01 Jun 2024 12:00:37 AM UTC)

1 0

(Possible breaking change) XML pages-articles dumps bug with missing revision text for some records; fix in progress with schema change
by Adam Baso 31 May '24

31 May '24

As described on Phabricator a bug [1] surfaced whereby the "pages-articles" XML dumps on https://dumps.wikimedia.org/ bear incomplete records. A possible fix has been identified, and it involves bumping the dump schema version from version 0.10 to version 0.11 [2], which could be a breaking change for some. MORE DETAILS: Due to the bug that surfaced, a nontrivial number of <text> nodes representing article text shows in a fashion like so as empty. <text bytes="123456789" /> A potential fix in T365155 [3] has been identified. Assuming further testing looks good, XML dumps will be kicked off again starting next week in order to restore the missing records as soon as possible. It will take a while for new dumps to be generated as it is a compute intensive operation. More progress will be reported at T365155 and new dumps will eventually show up on dumps.wikimedia.org . Although a number of pipelines may not notice the change associated with the schema bump, if your dump ingestion tooling or use of Special:Export relies on the specific shape of the XML at version 0.10 (e.g., because of code generation tools), please examine the differences between version 0.10 and version 0.11. One notable addition in version 0.11 is addition of MCR [4] fields. Thank you for your patience while this issue is resolved. -Adam [1] https://phabricator.wikimedia.org/T365501 [2] https://www.mediawiki.org/xml/export-0.10.xsd and https://www.mediawiki.org/xml/export-0.11.xsd Schema version 0.11 has existed in MediaWiki for over 6 years, but Wikimedia wikis have been using version 0.10. [3] https://phabricator.wikimedia.org/T365155#9851025 and https://phabricator.wikimedia.org/T365155#9851160 [4] https://www.mediawiki.org/wiki/Multi-Content_Revisions

1 0

31 May '24

Hello all, The next language community meeting is scheduled in a few weeks - May 31st at 16:00 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 is a participant-driven meeting, where we share language-specific updates related to various projects, collectively discuss technical issues related to language wikis, and work together to find possible solutions. For example, in the last meeting, the topics included the machine translation service (MinT) and the languages and models it currently supports, localization efforts from the Kiwix team, and technical challenges with numerical sorting in files used on Bengali Wikisource. Do you have any ideas for topics to share technical updates related to your project? Any problems that you would like to bring for discussion during the meeting? Do you need interpretation support from English to another language? Please reach out to me at ssethi(a)wikimedia.org and add agenda items to the document here: < https://etherpad.wikimedia.org/p/language-community-meeting-may-2024>. We look forward to your participation! Cheers, Jon, Mary, Oscar, Amir and Srishti *Srishti Sethi* Senior Developer Advocate Wikimedia Foundation <https://wikimediafoundation.org/>

1 2

🌱 Fresh 24.05 released!
by Krinkle 30 May '24

30 May '24

TLDR: fresh-node now defaults to Node.js 20, and introducing the "fresh-npm" security feature. Get started: https://gerrit.wikimedia.org/g/fresh#fresh-environment Changelog: https://gerrit.wikimedia.org/g/fresh/+/HEAD/CHANGELOG.md Commits: https://gerrit.wikimedia.org/r/q/project:fresh+is:merged Hi all, Fresh 24.05 is upon us! *What's new?* The fresh-node22 command has been introduced by James Forrester, and is now open for early testing. This uses the "releng/node22-test-browser" Docker image that is also available to Jenkins jobs in WMF CI. Standalone libraries and tools are welcome opt-in and switch their CI jobs in Zuul config if they pass under node22. The default fresh-node command was updated from Node.js 18 to Node.js 20, similarly re-using the same Docker images that we use in WMF CI. These feature the same Debian Linux version, same pre-installed packages, and versions thereof. This makes it as easy as possible to reproduce CI failures locally. Vice versa, if you use Fresh in local development, you're unlikely to encounter failures in CI. You can continue to develop on older versions via the fresh-node18 and fresh-node16 commands. The fresh-node14 command has been removed (unsupported since last year <https://github.com/nodejs/Release#end-of-life-releases>). This release includes the first contribution to Fresh by Marius Hoch (WMDE), who fixed a bug <https://gerrit.wikimedia.org/r/c/fresh/+/1034847> affecting projects with a space in their working directory name. Thanks Marius! Finally, this release introduces the experimental "fresh-npm" feature. You can opt-in by cloning the repo and running `bin/fresh-install --secure-npm`. This will shadow the npm command in the shell on your main workstation, and avoids accidentally running potentially insecure scripts outside Fresh. Other npm commands are unaffected. It can be bypassed as-needed by specifying the full path to npm, which is also printed at the end of any fresh-npm help or error message. I previously maintained this under the name "secpm" in a local patch <https://gerrit.wikimedia.org/r/c/fresh/+/675346> since 2021. It has served myself and a handful of others well. I hope it can be useful to others! To report issues or browse tasks, find us on Phabricator at https://phabricator.wikimedia.org/tag/fresh/. *What is Fresh?* Fresh is a fast way to launch isolated environments from your terminal. These can be used to work more securely and responsibly <https://timotijhof.net/posts/2019/protect-yourself-from-npm/> with Node.js-based developer tools, especially those installed from npm such as ESLint, QUnit, Grunt, Webdriver, and more. Example guide: https://www.mediawiki.org/wiki/Manual:JavaScript_unit_testing. Get started https://gerrit.wikimedia.org/g/fresh#fresh-environment -- Timo Tijhof, Principal Engineer, Wikimedia Foundation.

1 0

← Newer
1
...
4
5
6
7
8
9
10
...
2312
Older →

Jump to page:

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