Does not revert cleanly. Only workaround seems to be to roll back to commit before it.

Change 532296 merged by Marostegui:
[operations/software/tendril@master] tendril: Disable insert on innodb_trx and innodb_trx_log

Change 532333 merged by Vgutierrez:
[operations/puppet@production] ATS: Fix port definition on trafficserver::monitoring

The task was for Google-Code-in-2018 and is no more relevant.

 @CDanis I understand this is related to replicas for main traffic? as in not on specific groups? (ie: api).

Change 531875 merged by Vgutierrez:
[operations/puppet@production] ATS: Set origin TTFB timeout to 180 secs for TLS instance

+1

Change 531872 merged by Vgutierrez:
[operations/puppet@production] ATS: Allow specifying timeouts to TTFB in connections to origin servers

We had the issue since the first time we proceeded submodules. In short because we did something like:

find -name .gitmodules -execdir 'git submodule update --init'

PHP 5 is gone.

Git bisect points to rMWe4468a1d6b6b: Make LocalisationCache a service. Setting UBN! for attention. I feel this doesn't affect everyone, though, or it would have been noticed already.

I guess that is solved so :)

Change 532298 merged by Vgutierrez:
[operations/puppet@production] cache: Add use_trafficserver_tls parameter to unified profile

Low hanging fruits had been resolved at time. Then it is a never ending task to add CI and we would need a better process to have CI added at the moment the repositories are created.

Low hanging fruits had been resolved at time. Then it is a never ending task to add CI and we would need a better process to have CI added at the moment the repositories are created.

Low hanging fruits had been resolved at time. Then it is a never ending task to add CI and we would need a better process to have CI added at the moment the repositories are created.

I tried reproducing, but the file now has a licence that does not allow a transfer to Commons, so not possible :/

@Mathew.onipe can I ask further details on the error you get? It should definitely not be an issue if the test works in a docker image locally.

@Pginer-WMF , while talking to @Praveenp about Boost at ml.wp, this task was brought up again. I see that the related task was actually resolved recently, so I think you two could synch on what, if anything, is left to do here? Thanks!

Feature implemented and documented on https://wikitech.wikimedia.org/wiki/Varnish#HOWTO

In T231069#5434475, @Tgr wrote:

It makes little sense that having the page open would affect permission handling in any way. I'd just chalk this up to beta being slow.

@leila I just stumbled upon this task, and besides being happy that patch was merged I'm asking myself:

@Whatamidoing-WMF @Rmaung I thought https://meta.wikimedia.org/wiki/Community_Insights/Translation/2019/1-Invitation was the only message out there, then I stumbled on https://meta.wikimedia.org/wiki/Community_Insights/Translation/2019/General_information. I understand that the former is the one that Rebecca will need to deliver on wikis (the latter being for email only), but I appreciate confirmation.

Change 531873 merged by Ema:
[operations/puppet@production] VCL: add support for blacklisting IPs

Change 490117 had a related patch set uploaded (by Nikerabbit; owner: Jforrester):
[mediawiki/extensions/Translate@master] Hard-deprecate loading the extension via Translate.php

Change 532333 had a related patch set uploaded (by Vgutierrez; owner: Vgutierrez):
[operations/puppet@production] ATS: Fix port definition on trafficserver::monitoring

This is precisely to figure out if there is a meaningful difference in practice. I don't think there would be, I expect that the first paragraph is almost always included in the first paint for us.

Change 523779 merged by jenkins-bot:
[mediawiki/services/recommendation-api@master] Replace Wikidata Query Service with MediaWiki API

Change 482408 abandoned by Daimona Eaytoy:
Temporarily exclude Jobs from TitleMove hook

Tõlge valmib 30. septembri hommikuks.

For me the lesson learned is that if talking in technical terms about name servers or similar one should be super precise and not fall back to shortcut jargon, that might be common among technical experts. Our ISP first denied that they can let us configure name server of a domain that's not managed my them. I suppose if I would have been able to ask them about it correct terms, they would have confirmed already the first time (and I still don't understand what are the correct terms). It seems that differentiating among "owning domain" and "owning name servers" and "changing name servers" and "changing name server records" (and maybe even specific records) where appropriate would have helped much. Thanks for your patience and glad that everything worked out in the end!

Moving back to todo to get the list.

Change 532331 had a related patch set uploaded (by Mobrovac; owner: Mobrovac):
[operations/puppet@production] Scandium: Add the protocol to the rt-client config

That strikes me as rather dangerous. The caller has no way to know whether the result is safe to be used as HTML.

In T231119#5437018, @Yann wrote:

In T231119#5437008, @Joe wrote:

A file of 473 MB surely goes over the large file limits unless something changed recently.
https://commons.wikimedia.org/wiki/Help:Server-side_upload still seems to suggest you should request that. Untagging Operations as I don't think there is anything SRE should do here.

All of upload_by_url, bigChunkedUpload and the UploadWizard are supposed to allow uploads up to 4 GB. If that's not the case, please say it clearly and fix the documentation. Otherwise, this is a bug.

Change 532297 merged by Vgutierrez:
[operations/puppet@production] cache: Add missing tls_port parameter

Der Inhaltsplan der ersten Hälfte ist eingearbeitet. Das kann schon ausformuliert werden.
Die zweite Hälfte ist noch nicht überarbeitet, ist aber grob geplant.

Also, I am even more forward to keep disabling stuff we don't really use anymore, to see if we can reduce the weird memory growth that makes tendril crash after X months T231165: db1115 (tendril) paged twice in 24h due to OOM

This looks like the recurrent memory issues tendril has: T196726 however this time it doesn't HW issues

In T231119#5437008, @Joe wrote:

A file of 473 MB surely goes over the large file limits unless something changed recently.
https://commons.wikimedia.org/wiki/Help:Server-side_upload still seems to suggest you should request that. Untagging Operations as I don't think there is anything SRE should do here.

Change 530694 merged by Nischayn22:
[mediawiki/extensions/DocBookExport@master] Fix for T196760

Investigate the technical and UX considerations of requiring both a username and email address to successfully generate a password reset request email

This is a long way short of being a functional edit API. Have a look at ApiEditPage, it has 27 parameters, this proposal has 4. And there are controller-level complexities which are not represented here, like edit conflicts and CAPTCHA delivery. I don't know why we need this module or what kind of client the contributor is supposed to be using. If the idea is to provide feature parity with ApiEditPage, the design should start by looking at it.

Change 532250 merged by jenkins-bot:
[translatewiki@master] Use wfLoadExtension for Translate

Change 532298 had a related patch set uploaded (by Vgutierrez; owner: Vgutierrez):
[operations/puppet@production] cache: Allow setting an arbitrary redir_port

Change 532297 had a related patch set uploaded (by Vgutierrez; owner: Vgutierrez):
[operations/puppet@production] cache: Add missing tls_port parameter

A file of 473 MB surely goes over the large file limits unless something changed recently.