Wikitech-l November 2019

wikitech-l@lists.wikimedia.org

53 participants
71 discussions

The difference between fileexists-no-change and backend-fail-alreadyexists for action=upload
by Chen Xinyan 19 Nov '19

19 Nov '19

Hi there, Hope I've found the correct list for asking this question. I was setting up a CI test case for my MediaWiki Client Library to run a bot that will upload a file to https://en.wikipedia.beta.wmflabs.org in chunked stash mode. For most of the time, when I perform the final upload with filekey parameter, I will receive a fileexists-no-change error from the MW API server. This is expected, as there is already a same file with the same title on the site. However, today I received backend-fail-alreadyexists. The error message looks like backend-fail-alreadyexists: The file "mwstore://local-swift-eqiad/local-public/archive/9/95/20191116051316!Test_image.jpg" already exists. Does this error usually occurs when user tries to upload the same file? What's the difference between fileexists-no-change and backend-fail-alreadyexists? Thanks, Xinyan

2 2

s6 primary master switchover (read-only required) 19th Nov 05:00 AM UTC
by Manuel Arostegui 19 Nov '19

19 Nov '19

Hello, We have requested a 30 minutes read-only window for s6 wikis (T235475) for the 19th Nov from 05:00-05:30 AM UTC to switchover that section primary database master (T235469) db1061 is an old host and out of warranty that will be decommissioned (T217396). The new master will be db1131. We are going to do this on Tuesday 19th Nov from 05:00 to 05:30 AM UTC (we do not expect to use the 30 minutes window, if everything goes as expected). Impact: Writes will be blocked on the following wikis frwiki jawiki ruwiki Reads will remain unaffected. Communication will happen at #wikimedia-operations If you are around at that time and want to help with the monitoring, please join us! Thanks

1 2

Composer does not know mediawiki/mediawiki on dry-runs
by Stephan Gambke 17 Nov '19

17 Nov '19

When running `composer update` MediaWiki injects a mediawiki/mediawiki package, so extensions can declare a dependency on a particular MW version range. However, when doing a `composer update --dry-run` this package gets not injected causing the dry run to fail. Does anybody know a solution/workaround? Stephan

6 8

WM Technical Conference 2019 update - day 4
by Deb Tankersley 15 Nov '19

15 Nov '19

Hello and thanks for reading! We wanted to give a quick update on what happened during the final day of the Wikimedia Technical Conference <https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019>, in Atlanta, Georgia. *Friday <https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019/Program#…>, November 15, 2019:* The first morning session looked at LocalDev: complex multi-service MediaWiki development and use cases / personas that need tailored development environments (ticket <https://phabricator.wikimedia.org/T235372>). We also discussed API Integration Testing concentrating on functions, stories, and scenarios (ticket <https://phabricator.wikimedia.org/T234636>). After we dot voted on Thursday morning, we finished up the last unconference sessions on Friday: - New CI / Argo k8s for CI workloads challenges, details, paths forward ( ticket <https://phabricator.wikimedia.org/T238261>) - Wikimedia Space solves all your (communication) problems* (ticket <https://phabricator.wikimedia.org/T238237>) - The test pyramid and speeding up your results (ticket <https://phabricator.wikimedia.org/T234637>) - kiwix / open ZIM. portfolio software stack, future ?, tech needs - What is a technical contribution? (ticket <https://phabricator.wikimedia.org/T238262>) - JS Framework Experience Sharing (ticket <https://phabricator.wikimedia.org/T238264>) - Global templates! Let's flesh it out (ticket <https://phabricator.wikimedia.org/T238251>) - Logspam - how do we have less / surface it to the right people? (ticket <https://phabricator.wikimedia.org/T238250>) - PHPUnit: what can we improve, can we remove phpunit.php wrapper script, etc (ticket <https://phabricator.wikimedia.org/T238227>) - What user analytics would help you as a developer? (ticket <https://phabricator.wikimedia.org/T238274>) - I'll help you replace Travis with Actions for GitHub-mastered repos ( ticket <https://phabricator.wikimedia.org/T238244>) - The gradation of participation - what is a third party? Defining a common phrase with a common – and shared – understanding (ticket <https://phabricator.wikimedia.org/T238234>) - Ukulele to wikitext (ticket <https://phabricator.wikimedia.org/T238290> ) The last session was a Recap and Reflection gathering using a world cafe style discussion (ticket <https://phabricator.wikimedia.org/T238406>) - each of the 5 themes have a notes document that is in their respective epic tickets: - Local Development and onboarding (ticket <https://phabricator.wikimedia.org/T234087>) - Testing (ticket <https://phabricator.wikimedia.org/T234088>) - Deploying and Hosting (ticket <https://phabricator.wikimedia.org/T234089>) - Standardization Decisions (ticket <https://phabricator.wikimedia.org/T234090>) - People and Processes (ticket <https://phabricator.wikimedia.org/T234091>) We also did a group photo <https://commons.wikimedia.org/wiki/File:Wikimedia_Technical_Conference_2019…> in-between raindrops! We ended the day with our last documentation sprint, copying info from the day's sessions and moving them into the phabricator tickets (to keep all the data in one place), taking pictures of the session sticky notes / diagrams, and then adding them also into the phabricator tickets. whew! Photos and documentation that have been uploaded can be viewed using this category <https://commons.wikimedia.org/wiki/Category:Wikimedia_Technical_Conference_…> (look for day 4 <https://commons.wikimedia.org/wiki/Category:Wikimedia_Technical_Conference_…>) on Commons: Category:Wikimedia Technical Conference 2019 <https://commons.wikimedia.org/wiki/Category:Wikimedia_Technical_Conference_…> (sample demo: ukulele to wikitext <https://commons.wikimedia.org/wiki/File:Wikimedia_Technical_Conference_sess…> video). Cheers, The Wikimedia Technical Conference Program Committee -- deb tankersley (she/her) program manager, engineering Wikimedia Foundation

1 0

help once
by Fokou Joel 15 Nov '19

15 Nov '19

I am a student in the Faculty of Engineering and Technology in University of Buea(Cameroon). Thank you!

2 1

Re: [Wikitech-l] Composer does not know mediawiki/mediawiki on dry-runs
by Stephan Gambke 15 Nov '19

15 Nov '19

To enable extensions to declare a version constraint on MW, so an incompatible version of an extension is not installed in the first place instead of crashing MW later on. Stephan ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, November 15, 2019 4:27 PM, Florian Schmidt <florian.schmidt.welzow(a)t-online.de> wrote: > Extensions can express a dependency to mediawiki core in their extension.json. not sure where, how and why a non-existing composer package should be injected to a composer run. > > Am 15.11.2019 10:15 schrieb David Barratt <dbarratt(a)wikimedia.org>: > >> as far as I know, extensions shouldn't be declaring a dependency on >> MediaWiki in composer.json and if one is, it should probably be fixed. >> >> On Fri, Nov 15, 2019 at 9:50 AM Stephan Gambke via Wikitech-l < >> wikitech-l(a)lists.wikimedia.org> wrote: >> >>> >>> When running `composer update` MediaWiki injects a mediawiki/mediawiki >>> package, so extensions can declare a dependency on a particular MW version >>> range. >>> However, when doing a `composer update --dry-run` this package gets not >>> injected causing the dry run to fail. >>> >>> Does anybody know a solution/workaround? >>> >>> Stephan >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Wikitech-l mailing list >>> Wikitech-l(a)lists.wikimedia.org >>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l >> _______________________________________________ >> Wikitech-l mailing list >> Wikitech-l(a)lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/wikitech-l

1 0

Help
by Ayush Basral 15 Nov '19

15 Nov '19

Hey!! I am a new to wikimedia. Please help me to make my first contribution.

2 1

WM Technical Conference 2019 update - day 3
by Deb Tankersley 14 Nov '19

14 Nov '19

Hello, We wanted to give a quick update on what happened during day 3 of the Wikimedia Technical Conference <https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019>, in Atlanta, Georgia. *Thursday <https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019/Program#…>, November 14, 2019:* Morning sessions were all really good, and we did dot voting on unconference topics during our breaks. Afternoon was spent on a large portion of those unconference sessions. The morning sessions covered: - Self-service Stateless Microservices (for APIs) (ticket <https://phabricator.wikimedia.org/T234646>) - What have we learned when deploying a standalone server side rendering service for the new mobile Wikidata termbox (ticket <https://phabricator.wikimedia.org/T234642>) - The test pyramid and speeding up your results (ticket <https://phabricator.wikimedia.org/T234637>) - Mediawiki Code Ownership (ticket <https://phabricator.wikimedia.org/T234655>) - Running tests locally: an introduction (ticket <https://phabricator.wikimedia.org/T234638>) - Restructure Rest API and services (ticket <https://phabricator.wikimedia.org/T238257>) Afternoon sessions and unconferences: - Federated MediaWiki (ticket <https://phabricator.wikimedia.org/T238383>) - Language metadata in mediawiki (ticket <https://phabricator.wikimedia.org/T234644>) - RFCs / TechCom: how could RFCs be more useful (ticket <https://phabricator.wikimedia.org/T216308>) - Ideas for proposing changes to validating with our communities (ticket <https://phabricator.wikimedia.org/T238265>) - Automate wiki creation (ticket <https://phabricator.wikimedia.org/T238255> ) - Small things to improve in wikisources (ticket <https://phabricator.wikimedia.org/T238263>) - Interactive content at Wikimedia: how to even start (ticket <https://phabricator.wikimedia.org/T238259>) - CI counseling session 100% free (ticket <https://phabricator.wikimedia.org/T238275>) - Wikibase, Wikidata & things (ticket <https://phabricator.wikimedia.org/T238252>) - Movement Strategy 2030 - How do we know we are productive? Eng metrics (ticket <https://phabricator.wikimedia.org/T238384>) - MediaWiki Config mgmt @ scale (ticket <https://phabricator.wikimedia.org/T238273>) - WBStack.com Wikibase as a service (shared platform) MVP /prototype demo - Discourse extension for MediaWiki We ended the day with cleaning up documentation from the day's sessions and moving them into the phabricator tickets (to keep all the data in one place), taking pictures of the session sticky notes / diagrams, and then adding them also into the phabricator tickets. Photos and documentation that have been uploaded can be viewed using this category <https://commons.wikimedia.org/wiki/Category:Wikimedia_Technical_Conference_…> (look for day 3 <https://commons.wikimedia.org/wiki/Category:Wikimedia_Technical_Conference_…>) on Commons: Category:Wikimedia Technical Conference 2019 (sample media: unconference template <https://commons.wikimedia.org/wiki/File:WMTC19_unconference_template.jpg>). Cheers, The Wikimedia Technical Conference Program Committee -- deb tankersley (she/her) program manager, engineering Wikimedia Foundation

1 0

[Wikimedia Tech Talks] Wikidata, behind the curtain, 20, November, 2019 at 6PM UTC
by Sarah R 14 Nov '19

14 Nov '19

Hi Everyone, It's time for Wikimedia Tech Talks 2019 Episode 10! This talk will take place 20, November, 2019 at 6PM UTC. *Title: *Wikidata, behind the curtain *Speaker: *Amir Sarabadani, Software developer, Wikimedia Deutschland *Summary:* Wikidata is a complex and large-scale project. We all know how to use it and how to contribute to it but it's a little bit hard to understand how it actually works, how it scales and what parts are tricky about it. To lots of developers, it's a black box and this is not good. This talk plans to explain internals of Wikidata to other developers and explain future changes to Wikidata on its technical layer. The link to the Youtube Livestream can be found here: https://www.youtube.com/watch?v=uWqKyC7gt0s During the live talk, you are invited to join the discussion on IRC at #wikimedia-office You can watch past Tech Talks here: https://www.mediawiki.org/wiki/Tech_talks If you are interested in giving your own tech talk, you can learn more here: https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event#Te… *Note:* *Please feel free to distribute this email to any lists that you feel are appropriate!* Hope to see you there! Sarah R. Rodlund Technical Writer, Developer Advocacy <https://meta.wikimedia.org/wiki/Developer_Advocacy> srodlund(a)wikimedia.org

1 1

s1 (enwiki) primary master switchover (read-only required) 14th Nov 05:00 AM UTC
by Manuel Arostegui 14 Nov '19

14 Nov '19

Hello, We have requested a 30 minutes read-only window for s1 (enwiki) (T234801) for the 14th November from 05:00-05:30 AM UTC to switchover that section primary database master (T234800) db1067 is an old host and out of warranty that will be decommissioned (T217396). The new master will be db1083 We are going to do this on Thursday 14th Nov from 05:00 to 05:30 AM UTC (we do not expect to use the 30 minutes window, if everything goes as expected). Impact: Writes will be blocked on the following wiki: enwiki Reads will remain unaffected. Communication will happen at #wikimedia-operations If you are around at that time and want to help with the monitoring, please join us! Thanks

1 2

2026

2025

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 November 2019