Change 586163 had a related patch set uploaded (by Kevin Bazira; owner: Kevin Bazira):
[mediawiki/extensions/Jade@master] Added MW message key for jade-deleteendorsement

Let me know how you guys want to proceed with this and when :)

@Trizek-WMF @Tgr -- I haven't sent this survey privacy statement link to Legal yet. We need this one up on Foundation wiki right? To link to the Welcome Survey? Or are we not deploying Welcome Survey here?

Change 586162 had a related patch set uploaded (by BryanDavis; owner: Bryan Davis):
[operations/software/tools-webservice@master] Replace pykube with a custom API client

Mentioned in SAL (#wikimedia-operations) [2020-04-06T05:16:42Z] <vgutierrez> Enable inbound TLSv1.3 in upload@eqiad - T170567

Mentioned in SAL (#wikimedia-operations) [2020-04-06T05:16:21Z] <vgutierrez> Enable TLS Session Tickets on eqiad - T245616

Change 585697 merged by Vgutierrez:
[operations/puppet@production] ATS: Enable inbound TLSv1.3 on the upload cluster

Change 585697 merged by Vgutierrez:
[operations/puppet@production] ATS: Enable inbound TLSv1.3 on the upload cluster

Moving rows about within or between tables would be easier if each table was not a single solid block of data, but with each row separate and the central body of the table as a list of n pointers, if the table has n rows. Then, for i = 1(1)n the i-th pointer points to the i-th row. See https://en.wikipedia.org/wiki/Iliffe_vector

@eamedina this is how the "about wikipedia" 2nd page looks like, is it fixable on this PR?

As a note of support, I'd very much love to see support for glTF. There are so many amazing full colour models of NASA spacecraft, such as https://mars.nasa.gov/resources/24584/curiosity-rover-3d-model/

Is it a composer repo bug or a php bug causing non reproducible builds?

I'd like us to have the ability to reproducibly build composer phars before we start using upstream's binary files. I tried doing it just now and it seems like there's some very minor binary change:

(python3) user@dev ~/g/l/t/r/composer> diffoscope upstream.phar composer.phar
2020-04-05 18:57:22 W: diffoscope.main: Fuzzy-matching is currently disabled as the "tlsh" module is unavailable.
--- upstream.phar
+++ composer.phar
@@ -62,2407 +62,2407 @@
 000003d0: 0a0a 5f5f 4841 4c54 5f43 4f4d 5049 4c45  ..__HALT_COMPILE
 000003e0: 5228 293b 203f 3e0d 0ae8 9500 00f9 0100  R(); ?>.........
 000003f0: 0011 0000 0001 000d 0000 0063 6f6d 706f  ...........compo
 00000400: 7365 722e 7068 6172 0000 0000 2b00 0000  ser.phar....+...
 00000410: 7372 632f 436f 6d70 6f73 6572 2f41 7574  src/Composer/Aut
 00000420: 6f6c 6f61 642f 4175 746f 6c6f 6164 4765  oload/AutoloadGe
 00000430: 6e65 7261 746f 722e 7068 7051 6900 0035  nerator.phpQi..5
-00000440: 9167 5e51 6900 0010 24f8 e8b6 0100 0000  .g^Qi...$.......
+00000440: 9167 5e51 6900 0010 24f8 e8a4 0100 0000  .g^Qi...$.......

@SGautam_WMF can you check on the jio phone with the different languages?
The code is already on master, you just need to update your code and deploy.
These are the steps I'm thinking:
1-phone is in english
2-open app (should be in english)
3-open article and change article language to Marathi (for example)
4-app is still in english but article is in Marathi

Change 576166 merged by jenkins-bot:
[mediawiki/core@master] Add check to api that filters out expired watchlist items

In T249408#6030438, @Reedy wrote:

Bot username, if applicable (The "@whatever")

This is already in the subject, right? Just not in the body text?

That indeed looks very useful, pinging @Gehel and company (@EBernhardson and @dcausse) so thet know that if we have a verison of elastic that supports SQL access it can be made to "talk" to superset.

Change 586057 merged by Nuria:
[analytics/refinery/source@master] Add MeetingRoomApp to the bot regex

The bot detection running on shadow mode now should ba able to detect this case, ping @JAllemandou to verify.

Status: ❓
OS: macOS Catalina
Browser: Chrome
Device: MBP
Emulated Device: iPhoneX

Thank you!

Change 586155 had a related patch set uploaded (by Reedy; owner: Reedy):
[integration/config@master] dockerfiles: [composer-php70] Update composer to v1.10.1

Change 586155 had a related patch set uploaded (by Reedy; owner: Reedy):
[integration/config@master] dockerfiles: [composer-php70] Update composer to v1.10.1

Change 586154 had a related patch set uploaded (by Reedy; owner: Reedy):
[integration/config@master] Replace integration/composer repo with composer.phar

Bots don't seem to be working...

yeah right @srishakatux, Thanks a lot!!

https://www.mediawiki.org/wiki/Manual:How_to_debug/Login_problems

• The issue did not occur in chrome's incognito mode
• The issue did not occur with the remember flag enabled
• The issue did not occur on other wikis

...and its happening again

Change 584664 abandoned by Gaura87:
Core: Updgrade WebdriverIO version to 6 in mediawiki/core package.json file

In T249461#6030625, @Legoktm wrote:

In T249461#6030592, @bd808 wrote:

I honestly am not sure why we don't just use the upstream PHAR file, but I won't try to readjudicate that decision at this time.

Storing binary files in git isn't the greatest, and at the time we were using git to deploy composer to the various CI instances. But since we use docker now we can just keep the sha256sum in the repo and download the phar during the image build process and verify it then. 👍 from me.

In T249461#6030592, @bd808 wrote:

I honestly am not sure why we don't just use the upstream PHAR file, but I won't try to readjudicate that decision at this time.

Change 586144 had a related patch set uploaded (by Xqt; owner: Xqt):
[pywikibot/core@master] [cleanup] Decommission test_family.py

Change 586143 had a related patch set uploaded (by Gaura87; owner: Gaura87):
[mediawiki/extensions/AbuseFilter@master] AbuseFilter: Upgrade from webdriverio v4 to v5

In T249461#6030592, @bd808 wrote:

I honestly am not sure why we don't just use the upstream PHAR file, but I won't try to readjudicate that decision at this time.

@Petrb It happens on every click of any revid in the HAN where it's to do with another user making a revert.

Done.

I honestly am not sure why we don't just use the upstream PHAR file, but I won't try to readjudicate that decision at this time.

In T249461#6030590, @Reedy wrote:

It was more updating the platform restraint in composer.json for that repo. See my comment. We presumably don't need a version so low?

In T249461#6030588, @bd808 wrote:

In T249461#6030585, @Reedy wrote:

Seems we're still using composer with PHP 5.6 images?

https://github.com/wikimedia/integration-config/tree/e0982e0c4573e6dd32346d5e6499a881277f98d9/dockerfiles

v1.10.1 supports PHP >=v5.3.9 so this should not be a problem.

In T249461#6030585, @Reedy wrote:

Seems we're still using composer with PHP 5.6 images?

https://github.com/wikimedia/integration-config/tree/e0982e0c4573e6dd32346d5e6499a881277f98d9/dockerfiles

Seems we're still using composer with PHP 5.6 images?

Change 577745 merged by jenkins-bot:
[pywikibot/core@master] [cleanup] Move content of README-conversion.txt to Manual:Pywikibot

Change 586142 had a related patch set uploaded (by BryanDavis; owner: Bryan Davis):
[integration/composer@master] Update composer to 1.10.1

Correction : removing the spaces in the template solved the problem

I just tried to reset password and the emails appeared in gmail immediately.

The thing is I don't understand how could the stack jump from DisplayRevid to PostProcessEdit(), the function DisplayRevid doesn't have any call to that in it: