Wikitech-l July 2021

wikitech-l@lists.wikimedia.org

52 participants
45 discussions

Missing Section Headings
by Marc Riddell 13 Sep '24

13 Sep '24

Hello, I have been a WP editor since 2006. I hope you can help me. For some reason I no longer have Section Heading titles showing in the Articles. This is true of all Headings including the one that carries the Article subject's name. When there is a Table of Contents, it appears fine and, when I click on a particular Section, it goes to that Section, but all that is there is a straight line separating the Sections. There is also no button to edit a Section. If I edit the page and remove the "== ==" markers from the Section Titles, the Title then shows up, but not as a Section Heading. Also, I don't have any Date separators on my Want List. This started 2 days ago. Any thoughts? Thanks, Marc Riddell [[User:Michael David]]

10 11

How to make commits from mirrored Wikimedia repos show up on your GitHub profile
by Bartosz Dziewoński 27 Jun '24

27 Jun '24

I know it has been annoying a couple of people other than me, so now that I've learned how to make it work I'll share the knowledge here. tl;dr: Star the repositories. No, seriously. (And yes, you need to star each extension repo separately.) (Is there a place on mw.org to put this tidbit on?) ------- Forwarded message ------- From: "Brian Levine" <support(a)github.com> (GitHub Staff) To: matma.rex(a)gmail.com Cc: Subject: Re: Commits in mirrored repositories not showing up on my profile Date: Tue, 09 Jul 2013 06:47:19 +0200 Hi Bartosz In order to link your commits to your GitHub account, you need to have some association with the repository other than authoring the commit. Usually, having push access gives you that connection. In this case, you don't have push permission, so we don't link you to the commit. The easy solution here is for you to star the repository. If you star it - along with the other repositories that are giving you this problem - we'll see that you're connected to the repository and you'll get contribution credit for those commits. Cheers Brian -- Matma Rex

3 3

Research FAQ gets a facelift
by Dario Taraborelli 25 Jun '24

25 Jun '24

We just released a new version of Research:FAQ on Meta [1], significantly expanded and updated, to make our processes at WMF more transparent and to meet an explicit FDC request to clarify the role and responsibilities of individual teams involved in research across the organization. The previous version – written from the perspective of the (now inactive) Research:Committee, and mostly obsolete since the release of WMF's open access policy [2] – can still be found here [3]. Comments and bold edits to the new version of the document are welcome. For any question or concern, you can drop me a line or ping my username on-wiki. Thanks, Dario [1] https://meta.wikimedia.org/wiki/Research:FAQ [2] https://wikimediafoundation.org/wiki/Open_access_policy [3] https://meta.wikimedia.org/w/index.php?title=Research:FAQ&oldid=15176953 *Dario Taraborelli *Head of Research, Wikimedia Foundation wikimediafoundation.org • nitens.org • @readermeter <http://twitter.com/readermeter>

2 1

bluejeans
by Jeremy Baron 22 Feb '23

22 Feb '23

Hi, On Tue, Mar 1, 2016 at 3:36 PM, David Strine <dstrine(a)wikimedia.org> wrote: > We will be holding this brownbag in 25 minutes. The Bluejeans link has > changed: > > https://bluejeans.com/396234560 I'm not familiar with bluejeans and maybe have missed a transition because I wasn't paying enough attention. is this some kind of experiment? have all meetings transitioned to this service? anyway, my immediate question at the moment is how do you join without sharing your microphone and camera? am I correct thinking that this is an entirely proprietary stack that's neither gratis nor libre and has no on-premise (not cloud) hosting option? are we paying for this? -Jeremy

9 16

Unsubscribe from mail list
by Arpit Maheshwari 11 Jan '23

11 Jan '23

This is a request to please kindly unsubscribe me from your mailing list

4 4

List related to repositories which haven't mediawiki/mediawiki-codesniffer
by Zoran Dori 11 Jan '23

11 Jan '23

Hello, can someone to update list https://phabricator.wikimedia.org/P10500 which contains repositories which haven't mediawiki/mediawiki-codesniffer. I found in list that much repositories are empty, and repositories which aren't available on Gerrit. So, can someone please update this list of repositories (in mediawiki/extensions) which haven't mediawiki/mediawiki-codesniffer, but at least, contains one PHP file. or to provide me command with which I can update list when I want, so I don't need to request it every time. Best regards, Zoran. P. S.: Happy weekend! :)

4 6

Line numbering coming soon for syntax highlighting
by Johanna Strodt 22 Sep '21

22 Sep '21

// sorry for cross-posting Hello everyone, Here is another change from WMDE’s Technical Wishes team concerning syntax highlighting: Soon, line numbers will be shown in wikitext editors when you have the syntax highlighting feature (CodeMirror <https://www.mediawiki.org/wiki/Extension:CodeMirror> extension) enabled.[1] The change will make it easier to detect line breaks and to refer to a particular line in discussions. More information can be found on this project page. [2] We plan to deploy this with this week’s Mediawiki train, so it should be on wikis from April 13-15. As a first step, it will be available on the template namespace only. Deployment on other namespaces is planned for the near future. If you have any feedback, please let us know on the project’s talk page. [3] We hope line numbering will be useful to you! Johanna for the Technical Wishes team [1] https://www.mediawiki.org/wiki/Extension:CodeMirror [2] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Line_Numbering [3] https://meta.wikimedia.org/wiki/WMDE_Talk_Technical_Wishes/Line_Numbering -- Johanna Strodt Projektmanagerin Kommunikation Communitys Technische Wunschliste Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin Tel. (030) 219 158 26-0 https://wikimedia.de Unsere Vision ist eine Welt, in der alle Menschen am Wissens der Menschheit teilhaben, es nutzen und mehren können. Helfen Sie uns dabei! https://spenden.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207.

1 1

Action API: Removal of deprecated CSRF token parameters
by Petr Pchelko 26 Aug '21

26 Aug '21

TLDR: We will soon remove some parameters that were used to obtain CSRF tokens in the MediaWiki API. This will break bots, gadgets and user scripts that are still using these parameters. A significant and long delayed change to Action API is coming. API clients (user scripts, tools, etc) need to obtain a token before making write requests to MediaWiki over Action API. Up to MediaWiki 1.24 the action=tokens[1] and ‘token’ parameter in the following API endpoints were used to obtain a token: ‘rctoken’ in action=query&list=recentchanges [2] ‘rvtoken’ in action=query&prop=revisions [3] ‘intoken’ in action=query&prop=info [4] ‘ustoken’ in action=query&list=users[5] Since MediaWiki 1.24 these module and parameters were deprecated and were emitting deprecation warnings to API clients. These parameters and endpoint will now be removed from MediaWiki 1.37 and from Wikimedia installation. To obtain CSRF tokens clients now need to use a consolidated ‘action=query&meta=tokens’ endpoint. [6] Please respond to this email if you have any concerns or questions about this change. Petr Pchelko Staff Software Engineer Platform Engineering Team at WMF [1] https://en.wikipedia.org/w/api.php?action=help&modules=tokens <https://en.wikipedia.org/w/api.php?action=help&modules=tokens> [2] https://en.wikipedia.org/w/api.php?action=help&modules=query%2Brecentchanges <https://en.wikipedia.org/w/api.php?action=help&modules=query%2Brecentchanges> [3] https://en.wikipedia.org/w/api.php?action=help&modules=query%2Brevisions <https://en.wikipedia.org/w/api.php?action=help&modules=query%2Brevisions> [4] https://en.wikipedia.org/w/api.php?action=help&modules=query%2Binfo <https://en.wikipedia.org/w/api.php?action=help&modules=query%2Binfo> [5] https://en.wikipedia.org/w/api.php?action=help&modules=query%2Busers <https://en.wikipedia.org/w/api.php?action=help&modules=query%2Busers> [6] https://en.wikipedia.org/w/api.php?action=help&modules=query%2Btokens <https://en.wikipedia.org/w/api.php?action=help&modules=query%2Btokens>

3 3

Re: [MediaWiki-l] Replacing jQuery's hasClass() in MW extension JS code
by James Forrester 17 Aug '21

17 Aug '21

[Moving to wikitech-l; mediawiki-l is a little off-topic.] On Mon, 26 Jul 2021 at 21:27, Yaron Koren <yaron57(a)gmail.com> wrote: > Hi, > > I've been trying to get rid of the ESLint warnings for the JavaScript code > in some of my extensions, when they go through Jenkins validation. One > warning that appears fairly often is this one: > > Where possible, maintain application state in JS to avoid slower DOM > queries > no-jquery/no-class-state > > > I'm not sure if this is a warning that's specific to Wikimedia code, but > doing a web search on it brings up this Wikimedia help page as the only > real result: > > > https://github.com/wikimedia/eslint-plugin-no-jquery/blob/master/docs/rules… > Yes, we forked the dead "jquery" upstream eslint plugin and have expanded it significantly. In general, the plugin's purpose <https://www.npmjs.com/package/eslint-plugin-no-jquery> is to discourage use of jQuery functions, especially where the functions are deprecated or have faster native equivalents. (Almost all uses of jQuery are no longer necessary given that the vast majority of the Web only runs on modern-enough browsers.) This page is rather confusing. It says that the warning comes when calling > either hasClass() or toggleClass() on a jQuery element. That part makes > sense, but then the suggested alternatives are strange. The page says that > the following are some examples of bad code: > > $( 'div' ).hasClass(); > $div.hasClass(); > > In their place, it suggests the following: > > hasClass(); > [].hasClass(); > div.hasClass(); > No, it doesn't. It says that our code is clever enough to not think that these false positives are issues that you need to fix. It's not saying you should use a method called hasClass(); it's saying that you should maintain state inside JS; this is principally a performance/code smell test. If your code is triggered from a non-JS DOM (e.g. painted from PHP), the first time you grab state from the DOM is unavoidable (and so you'd use an inline disable), but thereafter you should keep track of such details in JS. An example of this is in the initialisation code for Notifications ("Echo"), where it has to grab the state from the DOM <https://gerrit.wikimedia.org/g/mediawiki/extensions/Echo/+/HEAD/modules/ext…> for a couple of items, but does so only once. Sorry that this is confusing! We could put together a narrow JS tips and tricks page and link to that from the linter, but most of these have been fixed over the years since we introduced this in Wikimedia production code so there's not been much call. J. -- *James D. Forrester* (he/him <http://pronoun.is/he> or they/themself <http://pronoun.is/they/.../themself>) Wikimedia Foundation <https://wikimediafoundation.org/>

2 1

Goto for microoptimisation
by Tim Starling 14 Aug '21

14 Aug '21

For performance sensitive tight loops, such as parsing and HTML construction, to get the best performance it's necessary to think about what PHP is doing on an opcode by opcode basis. Certain flow control patterns cannot be implemented efficiently in PHP without using "goto". The current example in Gerrit 708880 <https://gerrit.wikimedia.org/r/c/mediawiki/core/+/708880/5/includes/Html.ph…> comes down to: if ( $x == 1 ) { action1(); } else { action_not_1(); } if ( $x == 2 ) { action2(); } else { action_not_2(); } If $x==1 is true, we know that the $x==2 comparison is unnecessary and is a waste of a couple of VM operations. It's not feasible to just duplicate the actions, they are not as simple as portrayed here and splitting them out to a separate function would incur a function call overhead exceeding the proposed benefit. I am proposing if ( $x == 1 ) { action1(); goto not_2; // avoid unnecessary comparison $x == 2 } else { action_not_1(); } if ( $x == 2 ) { action2(); } else { not_2: action_not_2(); } I'm familiar with the cultivated distaste for goto. Some people are just parotting the textbook or their preferred authority, and others are scarred by experience with other languages such as old BASIC dialects. But I don't think either rationale really holds up to scrutiny. I think goto is often easier to read than workarounds for the lack of goto. For example, maybe you could do the current example with break: do { do { if ( $x === 1 ) { action1(); break; } else { action_not_1(); } if ( $x === 2 ) { action2(); break 2; } } while ( false ); action_not_2(); } while ( false ); But I don't think that's an improvement for readability. You can certainly use goto in a way that makes things unreadable, but that goes for a lot of things. I am requesting that goto be considered acceptable for micro-optimisation. When performance is not a concern, abstractions can be introduced which restructure the code so that it flows in a more conventional way. I understand that you might do a double-take when you see "goto" in a function. Unfamiliarity slows down comprehension. That's why I'm suggesting that it only be used when there is a performance justification. -- Tim Starling

10 11

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 July 2021