Hi all,
is there any research on common causes of Wikimedia production errors?
Based on recent examples, I plan to analyze and discuss how production
errors could be avoided. I am considering submitting a short paper on
that to the Wikidata workshop, with the deadline
Thursday, 20 July 2023
Website: https://wikidataworkshop.github.io/2023/
However, there might be better suitable venues.
I am also open to collaboration on this effort. If you are interested
in a joint paper, drop me an email until the end of this week.
All the best
Moritz
TLDR: The new "Excimer UI" option in WikimediaDebug generates flame graphs on-demand! Open this example <https://performance.wikimedia.org/excimer/profile/ab497e55783487c4> to browse a profile I captured earlier from Wikipedia's Main Page.
To learn what this feature is, why we built it, and when you might use it; read this week's post on the Techblog:
https://techblog.wikimedia.org/2023/06/08/flame-graphs-arrive-in-wikimediad…
Quick start: Capture your own profile
If you haven't already, install WikimediaDebug via Firefox Browser Add-ons <https://addons.mozilla.org/en-US/firefox/addon/wikimedia-debug-header/> or Chrome Web Store. <https://chrome.google.com/webstore/detail/wikimediadebug/binmakecefompkjggi…>
1. Navigate to an article on Wikipedia.
2. Set the widget to "On" with the "Excimer UI" option checked.
3. Reload the page.
A profile link is now appended to the WikimediaDebug popup. Click it!
Excimer can instrument pageviews, edits, search suggestions from the MediaWiki API, JavaScript loading (ResourceLoader load.php), and anything else served by MediaWiki from a WMF domain name—including Commons, Wikidata, and mediawiki.org.
--
Timo Tijhof,
Principal Engineer,
Performance Team,
Wikimedia Foundation.
Hi,
in German Wikipedia there are two incorrect entries in
https://de.wikipedia.org/wiki/Kategorie:Wikipedia:Seite_mit_Syntaxhervorheb…
This category is filled by Mediawiki software, something
like Syntaxhighlight-source-category or similar.
Please explain, how it's possible, that there are these two incorrect
entries of pages
with "<source>" indeed but commented out.
Thank you
Martin ...
{If you do not work on MediaWiki extensions or skins on Gerrit you can
safely ignore this email.}
If you are seeing this error in CI you will need to update your
ResourceModule definitions inside skin.json or extension.json to remove any
targets key in objects. If your code needs to be restricted to the Minerva
skin or all mobile skins please see
https://www.mediawiki.org/wiki/ResourceLoader/Migration_guide_for_extension…
for information.
This effectively marks the beginning of the end of the MobileFrontend
target system which has served us well for the last decade but has become
more of a nuisance as our codebases have matured meaning many new features
have not been enabled on the mobile site either intentionally or
accidentally. For more information around motivation at
https://phabricator.wikimedia.org/T127268. A test failure will now be
triggered for code trying to limit where code is loaded using this
mechanism.
If you are a developer with ResourceLoader module definitions that define
targets: [mobile,desktop] you can and should safely remove those.
Note, targets (for now) will continue to work in gadgets but may not in
future. Please join the conversation at
https://phabricator.wikimedia.org/T328610
Thanks for reading! Please feel free to reply with any questions.
Hi Nathan,
with "Wikimedia production error", I am referring to
https://phabricator.wikimedia.org/tag/wikimedia-production-error/, an
example is https://phabricator.wikimedia.org/T338381.
All the best
Moritz
On Thu, Jun 8, 2023 at 8:45 AM Nathan TeBlunthuis <nathante(a)uw.edu> wrote:
> Hi Physikerwelt, welcome, and thanks for your interest in opening a
> collaboration. I am not quite sure what you mean by a "Wikimedia
> production error". Suggest giving an example in a reply email to the list?
>
> Physikerwelt <wiki(a)physikerwelt.de> writes:
>
> > !-------------------------------------------------------------------|
> > This Message Is From an Untrusted Sender
> > You have not previously corresponded with this sender.
> > See https://itconnect.uw.edu/email-tags for additional
> > information. Please contact the UW-IT Service Center,
> > help(a)uw.edu 206.221.5000, for assistance.
> > |-------------------------------------------------------------------!
> >
> > Hi all,
> >
> > is there any research on common causes of Wikimedia production errors?
> >
> > Based on recent examples, I plan to analyze and discuss how production
> > errors could be avoided. I am considering submitting a short paper on
> > that to the Wikidata workshop, with the deadline
> > Thursday, 20 July 2023
> > Website:
> https://urldefense.com/v3/__https://wikidataworkshop.github.io/2023/__;!!K-…
> > However, there might be better suitable venues.
> >
> > I am also open to collaboration on this effort. If you are interested
> > in a joint paper, drop me an email until the end of this week.
> >
> > All the best
> > Moritz
> > _______________________________________________
> > Wiki-research-l mailing list -- wiki-research-l(a)lists.wikimedia.org
> > To unsubscribe send an email to
> wiki-research-l-leave(a)lists.wikimedia.org
>
> --
> Nathan TeBlunthuis
> Postdoctoral Research Fellow
> University of Michigan
> School of Information
> https://teblunthuis.cc
>
Hi All!
There will be *no deployment train the week of 2023-06-19 (Mon, 19 Jun –
Fri, 23 Jun).*
Mon, 19 Jun is the US holiday Juneteenth[0]—it is a no-deploy day.
Release Engineering will have a team-focused work week for the remainder of
the week. Backport and config deployments should continue as planned.
A long-term calendar of upcoming known deployment disruptions is available
on Wikitech[1].
Thank you!
Tyler Cipriani (he/him)
Engineering Manager, Release Engineering
Wikimedia Foundation
[0]: <https://en.wikipedia.org/wiki/Juneteenth>
[1]: <https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar>
Hey all,
On Monday June 5th, 2023 at 15:00 UTC (8am US/Pacific) we (the Release
Engineering Team) will run scripts[0] to add a bunch of users to the
/repos/mediawiki group[1] on GitLab. You may see mail from GitLab as a
result.
We're adding accounts from the wmf and ops LDAP groups, to be synchronized
regularly. We'll also be doing a one-time import of the mediawiki group
defined in Gerrit. Users will initially be added with a GitLab role of
"Developer". If a user has not yet logged into GitLab with their developer
account, this process will first create a GitLab account for them.
While there's a lot to be done yet, this is one step in migrating MediaWiki
development to GitLab. You can track our progress on this at T335921[2],
and review a draft of the proposed namespace layout and permissions policy
on mw.org[3].
Thanks!
-- Release Engineering
[0].
https://gitlab.wikimedia.org/repos/releng/gitlab-settings/-/tree/main/group…
[1]. https://gitlab.wikimedia.org/repos/mediawiki/
[2]. https://phabricator.wikimedia.org/T335921
[3]. https://www.mediawiki.org/wiki/GitLab/Policy#MediaWiki_namespace
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, May 3, 2023
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/>