Change 469091 had a related patch set uploaded (by Legoktm; owner: Legoktm):
[mediawiki/core@REL1_31] Update wikimedia/base-convert to 2.0.0

per requestor

Change 469076 merged by Bstorm:
[operations/puppet@production] sonofgridengine: Fix a typo, clean up a type we will never use and more.

Change 469077 had a related patch set uploaded (by Legoktm; owner: Legoktm):
[mediawiki/vendor@REL1_31] Update wikimedia/base-convert to 2.0.0

@Samwilson any progress on this? Is this stuck somewhere? Are we collecting data?

~1 month. This is on es.wiki - I'm not sure if that's what you mean by top
level site.

@Legoktm on reflection, I'm agreed entirely i.r.t "I don't think adding all oversighters and all checkusers to individual security tasks is a good idea" - there are a few other cases where general, non-security tasks are of immediate interest to the greater CU/OS community, but I'm not sure using an acl* project would be useful there.

Mentioned in SAL (#wikimedia-operations) [2018-10-22T20:06:57Z] <ladsgroup@deploy1001> Started deploy [ores/deploy@e89e880]: Use redis task tracker (T152012)

Change 469076 had a related patch set uploaded (by Bstorm; owner: Bstorm):
[operations/puppet@production] sonofgridengine: Fix a typo, clean up a type we will never use and more.

@atgo: 100K clickthrough over what period of time? What is the top level site?

Change 469075 had a related patch set uploaded (by Legoktm; owner: Legoktm):
[mediawiki/vendor@REL1_32] Update wikimedia/base-convert to 2.0.0

Actually, scratch that. It was just a simple typo buried in my refactor.

There's a similar task requesting PHP 5.x tests against older core versions for i18n extensions that I can't find right now, but it's the same basic ask.

Update: When using Firefox, the network tab DOES show a response, but the dialog still shows the entire template as if TemplateData doesnt' exist.

Security tasks are generally kept to a limited audience of MediaWiki developers plus a few other people. We created an ACL for stewards because there was a repeated need to add them to individual tasks, and they're already an incredibly trusted group of people who are relatively well known to developers, and are familiar with our workflows.

Thank you, @Ejegg

In T114401#4686487, @GTirloni wrote:

If you search for "ptrace escape container", you may start to share my concerns. The Linux security mechanisms are porous and I wouldn't trust simple same-process-UID restrictions considering there have been other methods to abuse ptrace and increase privileges.

Are you serious? @WingedBladesofGodric is one of the few people who has been willing to actually help us out over at New Page Patrol with the list of tasks that have languished for years (some of which are apparently very simple to accomplish). We are all very sick of being pointed in the direction of the Wishlist even for fixing bugs which have existed in the software for years (like the one that makes using it for AfD impossible on second AfDs).

I‘ll restart last tests

It still happens, even after T158123: Deploy kartotherian-snapshot v0.3.0 to production

Change 469045 merged by jenkins-bot:
[mediawiki/extensions/MobileFrontend@master] Moving mobile.startup/Drawer.js to webpack

This seems like it would be pretty useful.

When we have a large section of subtasks with more sub-subtasks in a general task the tree is very long. Collapsing it by subtasks and making them expandable would be the idea.

I think if we want to show both, we would have to put the currency symbol in parens after the amount. The fancy localization function we use to get the currency symbol also decides whether to put the symbol before or after the amount, as appropriate (and also selects the right char to use as the decimal separator). So how does this look?

$1.25 (1.25 MXN)

Where are the labsdb hosts going to live if they are being moved out of the labs-support VLAN? Likely these cloud-analytics nodes should live wherever labdb lives.

Change 469069 had a related patch set uploaded (by Awight; owner: Awight):
[integration/config@master] [WIP] Match rule for MediaWiki current TLS

Right now, 8: 3 ganeti instances and 5 bare metal worker nodes. We wouldn't be adding more nodes in within this FY, but depending on data size and demand, we might add more next FY. If we did, I'd expect +3 more worker nodes. But, 5 might be enough for quite a while too.

So the partially refactored bit with the "resource" resource type breaks the queue config. I either have to undo a lot of that or just use a different type with the same provider, pretty much.

@TBolliger, what exactly are we trying to get out of these numbers?

Looks like the issue was fixed in rEKAR40d2e6efe81b: Allow mapframe without geoJSON in VE.

Change 469067 had a related patch set uploaded (by Jforrester; owner: Legoktm):
[mediawiki/core@REL1_32] Update wikimedia/base-convert to 2.0.0

How many servers are we talking about both right now, as well as in the mid-term e.g. in the next year or two?

Change 469047 merged by jenkins-bot:
[mediawiki/core@master] Update wikimedia/base-convert to 2.0.0