Wikitech-l January 2023

wikitech-l@lists.wikimedia.org

37 participants
33 discussions

Upcoming shutdown of osmdb.eqiad.wmnet
by Andrew Bogott 31 Jan '23

31 Jan '23

The hardware that hosts osmdb.eqiad.wmnet is long past its end of life and will be shut down on February 12th. WMF staff do not plan to support that database after that date, and the domain will be shut down. I am pretty sure that we have already made arrangements with all current users of the service, but I'm sending this email out of an abundance of caution. If you think you are using it, please chime in on the associated phabricator ticket[0] so that we know you exist! There is a volunteer-maintained replacement that you should be able to switch to with a minimum of effort. Thanks for reading! -Andrew + the WMCS team [0] https://phabricator.wikimedia.org/T323159

1 0

Help to fix request
by Esteban Zarate 31 Jan '23

31 Jan '23

Hi, I need the list of uploaders in the category Category:Uploaded via Campaign:Wikivacaciones 2022, I did https://quarry.wmcloud.org/query/70909 based in another request but it doesn't work, anyone can fix it? Regards!!

2 2

MediaWiki Language Extension Bundle 2023.01
by Kartik Mistry 25 Jan '23

25 Jan '23

We would like to announce the release of MediaWiki Language Extension Bundle 2023.01. This bundle is compatible with '''MediaWiki >= 1.38.0''' and requires '''PHP >= 7.4.0'''. The next MLEB is expected to be released in 3 months. If there are very important bug fixes, we will do an intermediate release. Please give us your feedback at [[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]]. * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2023.01.tar… * sha256sum: 47dac8f27c363fb03ac2dfab023e45fa6cae9a5a03c4271961052bdf0b5aa497 * Signature: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2023.01.tar… Quick links: * Installation instructions are at: https://www.mediawiki.org/wiki/MLEB * Announcements of new releases will be posted to a mailing list: https://lists.wikimedia.org/postorius/lists/mediawiki-i18n.lists.wikimedia.… * Report bugs to: https://phabricator.wikimedia.org/project/view/1464/ A detailed release note for this release can be found at: https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle/2023.01 -- Kartik Mistry | કાર્તિક મિસ્ત્રી kartikm.wordpress.com

1 0

Purge cache for mobile users
by Pavel Spacek 23 Jan '23

23 Jan '23

Hi, Hope this is the right channel for solving the issue. Varnish has been implemented a year ago, excellent response, working fine. But after installation of Mobilefrontend several months later the issues were detected. (mediawiki 1.38.2, varnish 7.1) Purges after the page updates run and purge desktop entries automatically as well, but when the same page is accessed from the mobile device, the old page version before the update is shown, the mobile entry has not been purged. Mobilefrontend is installed and configured as advised in mw:Extension:MobileFrontend/Configuring_browser_auto-detection option 2, same domain. The only difference between requests for desktop/mobile version is in the header x-subdomain: no for mobile version (shows during the debug in varnishlog). But even curl sending this header for purge request did not work. Configuration: Mediawiki: wfLoadExtension( 'MobileFrontend' ); $wgMFAutodetectMobileView = true; $wgMinervaEnableSiteNotice = true; $wgMFDefaultSkinClass = 'SkinMinerva'; ... $wgInternalServer = "http://127.0.0.1:8080"; $wgUseCdn = true; $wgCdnServers = array(); $wgCdnServers[] = "127.0.0.1:8080"; Varnish: According https://www.mediawiki.org/wiki/Manual:Varnish_caching, it had to be customized, the page is little out-of-date and according to: https://www.mediawiki.org/wiki/Extension:MobileFrontend/Configuration a https://www.mediawiki.org/wiki/Extension:MobileFrontend/Configuring_browser… . In sub vcl_recv { .... if (req.method == "PURGE") { if ((req.http.X-Forwarded-For == "ip address") || (req.http.X-Forwarded-For == "ip address") || (req.http.X-Forwarded-For == "ip address")) { set req.http.host = "host"; return (hash); } else { return (synth(405, "Not allowed")); } } ... unset req.http.x-subdomain; # Requester shouldn't be allowed to supply arbitrary X-Subdomain header if (req.http.User-Agent ~ "(?i)^(lg-|sie-|nec-|lge-|sgh-|pg-)|(mobi|240x240|240x320|320x320|alcatel|android|audio vox|bada|benq|blackberry|cdm-|compal-|docomo|ericsson|hiptop|htc[-_]|huawei|ipod|kddi-|kindle|meego|midp|mitsu|mmp\/|mot- |motor|ngm_|nintendo|opera.m|palm|panasonic|philips|phone|playstation|portalmmm|sagem-|samsung|sanyo|sec-|sendo|sharp|sof tbank|symbian|teleca|up.browser|webos)") { set req.http.x-subdomain = "no"; } ... return (hash); ... sub vcl_hash { # Cache the mobile version of pages separately. # # NOTE: x-subdomain header should only have one value (if it exists), # therefore vcl_recv() should remove user-supplied X-Subdomain header. hash_data(req.http.x-subdomain); } ... import purge; sub my_purge { set req.http.purged = purge.soft(0s,30s); if (req.http.purged == "0") { return (synth(404)); } else { return (synth(200)); } } After the purge if someone does not request the page and it would not be loaded into cache, after 30 seconds the page should be loaded automatically. The consequence of the issue is that mobile users do not see up-to-date versions of the pages, the only workaround is restart varnish. Thanks for advice pointing to the solution. Pavel Spacek

1 0

JSON of Lint errors list
by Martin Domdey 19 Jan '23

19 Jan '23

Hi! Is it possible to parse a JSON of this Lint errors list, maybe by API or anyhow? https://en.wikipedia.org/w/index.php?title=Special:LintErrors/obsolete-tag&… Thank you Martin ...

3 3

Avoid invisible characters in page titles
by Martin Domdey 17 Jan '23

17 Jan '23

Hi, isn't it better to avoid invisible characters in page titles while creating the pages? Please look here, there has been problems with invisible characters working with it when parsing or page linking those page titles with invisible unicode characters: https://de.wikipedia.org/wiki/Benutzer_Diskussion:Wurgl#Liste_der_Biografie… Instead of this there will never be a problem when invisible characters within the page title name will be deleted when creating the page. What do you think about it and what technical approaches do already exist? How are LTR and RTL marks dealt if creating pages with them? Thank you very much and kind regards Martin aka user:Doc_Taxon

4 4

OOUI window manager
by Igal Khitron 16 Jan '23

16 Jan '23

Hello. Could you tell me, please, is there a way to check if a window exists in manager by its symbolic name? hasWindow() does not except such a name. getWindow() returns empty window if it was not exists before. getWindow()...isInitialized() is always true. All I need is to check if the window "win1" exists, and if it's not, create it. Thank you. Igal (User:IKhitron)

2 2

Cloud VPS users, please claim your projects
by Andrew Bogott 12 Jan '23

12 Jan '23

Hello cloud-vps users! It's time for our annual cleanup of unused projects and resources. Every year or so the Cloud Services team tries to identify and clean up unused projects and VMs. We do this via an opt-in process: anyone can mark a project as 'in use,' and that project will be preserved for another year. I've created a wiki page that lists all existing projects, here: https://wikitech.wikimedia.org/wiki/News/Cloud_VPS_2022_Purge If you are a VPS user, please visit that page and mark any projects that you use as {{Used}}. Note that it's not necessary for you to be a project admin to mark something -- if you know that you're currently using a resource and want to keep using it, go ahead and mark it accordingly. If you /are/ a project admin, please take a moment to mark which VMs are or aren't used in your projects. When February arrives, I will shut down and begin the process of reclaiming resources from unused projects. If you think you use a VPS project but aren't sure which, I encourage you to poke around on https://tools.wmflabs.org/openstack-browser/ to see what looks familiar. Worst case, just email cloud(a)lists.wikimedia.org with a description of your use case and we'll sort it out there. Exclusive toolforge users are free to ignore this email. Thank you! -Andrew and the WMCS team

1 2

major upgrade of PageProperties extension (a proof of concept for the use of SLOTS)
by tdvit＠mail.com 12 Jan '23

12 Jan '23

4 5

help mediawiki extension
by Tim Moody 12 Jan '23

12 Jan '23

On MW 1.39.0 and .1 and PHP 8.1.2-1ubuntu2.9, I am trying to revise a parserhook extension to mediawiki that uses wfParseUrl(). https://doc.wikimedia.org/mediawiki-core/master/php/GlobalFunctions_8php.ht… says that is deprecated and I should use UrlUtils::parse(). The former looks like a function and the latter looks like a class, perhaps a subclass of Utils. My first question is what if any use statement do I need. The extension already has use Html, but use UrlUtils gives an error because it can't be found. Do I need to instantiate Utils or UrlUtils and invoke the urlparser as $urlUtils -> parse()? When I invoke UrlUtils::parse I get a complaint about calling a non-static method statically. The old code was $url_parts = wfParseUrl( $graph_url ); and the new $url_parts = UrlUtils::parse( $graph_url ); Any help would be appreciated. Tim

3 4

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 January 2023