The next release of Scap, our deployment tool, renames the "scap sync"
subcommand to "scap sync-world". The sync command should mostly only
be used by Release Engineering during train deployments, and SWAT
folks updating l10n; everyone else almost certainly wants "scap
sync-file" instead. The change is to make it harder to use the wrong
command by mistake.
If you know of another use of "scap sync", especially in a script
rather then interactive use, please tell me as soon as possible, by
leaving a comment on this Phabricator task:
https://phabricator.wikimedia.org/T250302
The next release will probably happen within a few weeks. After that
"scap sync" will be an error, with a message suggesting "scap
sync-world" or "scap sync-file" as a replacement. (Which is OK for
interactive use, but might be problematic for scripts.)
--
WMF release engineering team | he/him or they/them
"Imagine a world in which every single human being can freely share in
the sum of all knowledge."
Forwarding.
Pine
( https://meta.wikimedia.org/wiki/User:Pine )
---------- Forwarded message ---------
From: Amir E. Aharoni <amir.aharoni(a)mail.huji.ac.il>
Date: Mon, May 25, 2020 at 7:22 PM
Subject: [Wikimedia-l] Language Showcase, May 2020
To: wikimedia-l <wikimedia-l(a)lists.wikimedia.org>
Hello,
This is an announcement about a new installment of the Language Showcase, a
series of presentations about various aspects of language diversity and its
connection to Wikimedia Projects.
This new installment will deal with the latest design research about the
upcoming section translation feature for Content Translation.
This session is going to be broadcast over Zoom, and a recording will be
published for later viewing. You can also participate in the conversation
on IRC or with us on the Zoom meeting.
Please read below for the event details, including local time, joining
links and do let us know if you have any questions.
Thank you!
Amir
== Details ==
# Event: Language Showcase #5
# When: May 27, 2020 (Wednesday) at 13:00 UTC (check local time
https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200527T1300 )
# Where:
Join Zoom Meeting
https://wikimedia.zoom.us/j/97081030000
Meeting ID: 970 8103 0000
IRC - #wikimedia-office (on Freenode)
# Agenda:
The latest design research about the upcoming section translation feature
for Content Translation.
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
_______________________________________________
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l(a)lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
Hi folks,
Is there a page where I can find a matrix or some other executive summary
of what players we're using on what browsers?
Also, how can one force the use of a certain player? I'm asking because
I've tried to push for more video to be used in Infoboxes just to see
examples of why that is a terrible idea [1]. Now, I strongly suspect that
the issue is the Infobox code rather than the player, but I'm not sure how
to debug it, since I see the videojs on all my browsers.
Strainu
[1] https://ro.wikipedia.org/wiki/Fi%C8%99ier:IMG_20200523_183135.jpg
Hello,
We will switch the CI services from contint1001 (eqiad) to contint2001
(codfw). The maintenance is scheduled for Wednesday May 27th 9:30 CEST
(7:30 UTC).
The maintenance window is TWO HOURS, but the migration will most
probably be complete in a shorter time frame.
We previously tried the upgrade on May 11st which got rollbacked since I
have missed the java 8 to 11 upgrade which turned out to be a deal breaker.
During the maintenance, CI will not be available: no tests will be run
and events (code-review +2, rebase, new patchsets) will not be captured.
The beta cluster will NOT be automatically updated.
If a change has to happen on the configuration repositories:
* operations/puppet :
locally run:
- bundle update && bundle exec rake test
or if you have Docker:
- $puppet_dir/utils/run_ci_locally.sh
* operations/mediawiki-config :
locally run: composer install && composer test
Then manually V+2 and Submit the change.
After the maintenance, Antoine will retrigger most events.
The related ticket is: https://phabricator.wikimedia.org/T224591
Synchronization will happen on IRC in #wikimedia-operations
--
Antoine "hashar" Musso
Hello,
The 1.35.0-wmf.32 train is deployed on group 0 / 1.
It has been blocked due to a large increase of writes on the databases
(T247028). An issue that will need coordination with the database
administrators for monitoring.
There is also a regression in the Vector skin which prevents adding
links in other languages when the page does not have any links yet. T252800.
* https://phabricator.wikimedia.org/T247028
* https://phabricator.wikimedia.org/T252800
We are in a bit odd position since this week had no train deployment
planned. We might try to push 1.35.0-wmf.32 to the remaining wikis this
week, but most probably we might end up delaying until Monday May 25th.
cheers,
--
Antoine "hashar" Musso
SelectQueryBuilder is a new fluent interface for constructing database
queries, which has been merged to master for release in MediaWiki
1.35. Please consider using it in new code.
SELECT page_id FROM page
WHERE page_namespace=$namespace AND page_title=$title
becomes
$id = $db->newSelectQueryBuilder()
->select( 'page_id' )
->from( 'page' )
->where( [
'page_namespace' => $namespace,
'page_title' => $title,
] )
->fetchField();
As explained on the design task T243051, SelectQueryBuilder was
loosely based on the query builder in Doctrine, but I made an effort
to respect existing MediaWiki conventions, to make migration easy.
SelectQueryBuilder is easy to use for simple cases, but has the most
impact on readability when it is used for complex queries. That's why
I chose to migrate the showIndirectLinks query in
Special:WhatLinksHere as a pilot -- it was one of the gnarliest
queries in core.
SelectQueryBuilder excels at building joins, including parenthesized
(nested) joins and joins on subqueries.
SelectQueryBuilder can be used as a structured alternative to the
"query info" pattern, in which the parameters to Database::select()
are stored in an associative array. It can convert to and from such
arrays. As a pilot of this functionality, I converted ApiQueryBase to
use a SelectQueryBuilder to store accumulated query info.
Check it out!
-- Tim Starling
Hi,
we've released v0.39.0 of the OOUI library this Tuesday. It will rollout on
the
normal train next Tuesday, 26 May.
Highlights in this release:
- Text flow of form layouts on mobile devices was improved, surfaced
in Advanced Mobile Contributions
- Additionally this release removed deprecated icons 'beaker' and
'unTrash', both were renamed, former to 'labFlask', latter to
'restore'. Additionally 'toc' in 'icons-layout' was deprecated in this
release, as design team has decided to use 'listBullet' as unified
table of contents icon.[0]
- Added option in PopupWidget to remove close button and add custom icon to
widget head. Thanks to volunteer contributor Sohom Datta!
- Remove `onLookupMenuItemChoose` event in LookupElement. It got deprecated
in v0.35.2. Use onLookupMenuChoose instead.
- TagItemWidget: Remove `setDisabled` function. It was deprecated in
v0.27.0.
Please look through your code, if you still occur to use them.
- Underlying library OOjs was updated to v5.0.0, up from v3.0.1,
nominally a breaking change.
Also, as new features of OOUI v0.38.0, ButtonMenuSelectWidget and
IndexLayout.php#setTabPanel was newly implemented.
You can find details on additional new features, code-level, styling
and interaction design amendments, and all improvements since v0.38.0
in the full changelog[0].
If you have any further queries or need help dealing with breaking
changes, please let me know.
As always, interactive demos[1] and library documentation is available
on mediawiki.org[2], there is comprehensive generated code-level
documentation and interactive demos and tutorials hosted on
doc.wikimedia.org[3].
OOUI version: 0.39.0
MediaWiki version: 1.35.0-wmf.34
Date of deployment to production: Regular train, starting Tuesday 26 May
[0] - https://gerrit.wikimedia.org/g/oojs/ui/+/v0.39.0/History.md
[1] -
https://doc.wikimedia.org/oojs-ui/master/demos/#widgets-mediawiki-vector-ltr
[2] - https://www.mediawiki.org/wiki/OOUI
[3] - https://doc.wikimedia.org/oojs-ui/master/
Best,
Volker
Hello WMF shell users,
all of you have access to the backend behind https://people.wikimedia.org/
where you can publish your own files.
The backend for this is a dedicated VM running on ganeti which until today
was people1001.eqiad.wmnet running on stretch (Debian oldstable).
Today it has been replaced by people1002.eqiad.wmnet running on buster
(Debian stable).
All your files have already been rsynced over. You should not have to
do anything except remember to now use people1002 instead of
people1001 when uploading new files.
I have already removed access to people1001 to avoid uploads there but
files have not been deleted and I will keep it up for another day or
so just in case.
https://wikitech.wikimedia.org/wiki/People.wikimedia.org (general info
about the service)
https://wikitech.wikimedia.org/wiki/People1002 (you can find the
fingerprints of the new server here)
Ticket if any unexpected issues: https://phabricator.wikimedia.org/T247649
--
Daniel Zahn <dzahn(a)wikimedia.org>
Operations Engineer
