Are you suggesting to remove 'hideuser'?

In T213993#4888885, @Paladox wrote:

Is there any way to support multiple php versions in luasandbox without needing for it to be recompiled?

You built it though, you didn't install from a precompiled package.

I believe this falls under the editing team, since the button is created by VisualEditor. @Esanders please correct me if I'm wrong

@Pcoombe unfortunately the available versions on Jessie (current OS) and Stretch (upcoming OS) are both old (0.14 and 0.18 respectively). Buster (2 OS versions out) has 1.0 but that's a ways off. So we'd want to look at packaging it ourselves which is doable, unless someone around here (analytics?) has already done that which would be easier.

In T213429#4881119, @Esanders wrote:

In T213429#4869866, @iamjessklein wrote:

• In Source editing mode, selecting to edit the whole article only shows the intro section when it should reveal the entire article

This was a deliberate decision made by the then mobile team, I believe made for performance reasons. I think there is a separate ticket about create separate links for edit-whole-document and edit-lede-section. I have an update to the patch which matches this behaviour in visual mode (so it edits the lede section). If we want to change this is should be consistent in both modes and we should be aware it would be a big change to the current mobile wikitext experience.

Change 485072 had a related patch set uploaded (by Mathew.onipe; owner: Mathew.onipe):
[operations/puppet@production] maps: change cassandra version

Change 485013 merged by jenkins-bot:
[mediawiki/extensions/Popups@master] Rename current gateway to pagePreviewGateway

In T119043#4887415, @akosiaris wrote:

In T119043#4885517, @Yurik wrote:

Most of the time, Vega is used via a template, because otherwise you have a massive copy/paste of code without any benefit, while having no way to fix issues or improve appearance of all graphs en mass. Thus, per what @Anomie said - MCR is an orthogonal (in its current form) to the generated content. This actually has more similarities with the image thumb service than MCR (content is generated from "master" - wiki markup, and cached for usage by both the rendering service like Graphoid and directly from the client via the dynamic graph loading).

This does contradict however with requirement 6. BonusB: When user looks at an older revision of an article, they should see the graphs for that revision. given above. Just noting it, effectively reiterating what I think Tim has better phrased it in his comment at T119043#1868557

Change 485016 merged by jenkins-bot:
[mediawiki/extensions/Popups@master] Introduce TYPE_REFERENCE constant in advance

Yes, that wound up being there.

user_properties is not the best case for one-off sqoop, because it is constantly updated.
We would benefit from a real time approach, but this is not going to happen in the near future.

Security review was completed in Dec. 2018. The patch should now pass tests and is awaiting code review.

Change 483068 merged by jenkins-bot:
[mediawiki/extensions/WikibaseLexeme@master] Cleanup commented out tests in LexemeSensesMergerTest

Change 485070 merged by Elukey:
[operations/puppet/cdh@master] check_hdfs_active_namenode: find cluster name in the config

5% gives us around 0.6 - 0.8 jobs per second

Yeah, this was by design for the reasons listed by @Trizek-WMF. We could thinking about persisting the question text per unique page (so typing "ABC" in the help panel on Page X and "DEF" on page Y, closing both, opening Page X you'd see "ABC" and opening page Y you'd see "DEF") but that seems like over-engineering to me.

https://github.com/wmde/Euro/pull/9

Looks good to me on 2.7.269-alpha-2019-01-16

@Zoranzoki21 do you have an ETA for when this will be available? I am not familiar with how the code gets added/merged.

Although the title refers to a specific issue with Help panel that was Resolved, the task has some insights on more general fixes that need to be added. Removing Growth team project related tags.

Change 485070 had a related patch set uploaded (by Elukey; owner: Elukey):
[operations/puppet/cdh@master] check_hdfs_active_namenode: find cluster name in the config

Thank you, @Jdforrester-WMF!

Sorry, yes, but didn't want to bypass any Core Platform Team processes.

Change 359184 abandoned by Jforrester:
Deprecate Content::getNativeData, add TextContent::getText

Mentioned in SAL (#wikimedia-operations) [2019-01-17T17:38:02Z] <addshore@deploy1001> Synchronized wmf-config/InitialiseSettings.php: ConstraintsCheckJobs on wikidatawiki (5% of edits) T204031 (duration: 00m 52s)

Thanks for clarifying! Okay, one more question for @Abit & @Ramsey-WMF just so everyone is on the same page. The statistic you want is: the % of all uploaded files which have had additions to their pages in the first 2 months after upload.

Change 484625 merged by jenkins-bot:
[operations/mediawiki-config@master] wikidata: post edit constraint jobs on 5% of edits

Replication flowing, I am glad we migrated most of those MyISAM tables away, so far it is working fine

As a last resort, the data could always be stored as userjs-* user settings. The limitation there (apart from being an ugly hack) is that the data needs to be small, but AIUI we are just talking about a few numbers here.

I got it working on my server and so it does work

Change 485044 merged by Vgutierrez:
[operations/puppet@production] pybal: check for discrepancies in the configured services

@phuedx as far as I could see Puppeteer does not provide a method for response interception. Some people intercept the request, then make a new request directly from the intercept handler callback and return that, but that seems a bit fragile.

In T214003#4888702, @Majora wrote:

In T214003#4888247, @AlexisJazz wrote:

In T214003#4888199, @DonTrung wrote:

Would this then also automatically give these permissions to "patrollers"?

Autopatrol is included in patrol.

That's actually not how that works @AlexisJazz. You have to separate user groups from user rights/flags. Flags are assigned to groups and then the group is granted to editors. Right now both the autopatrolled and patroller groups have the "autopatrol" flag. The discussion and consensus at the pump was to grant the "upload_by_url" flag to the autopatroller group (which would have made the extended uploader group a duplicate). There was no talk of, and no consensus, to add this flag to the patroller group. So to answer @DonTrung, no. The flag will not be granted to patrollers.

Is there any way to support multiple php versions in luasandbox without needing for it to be recompiled?

Also, the patch provided does not log the user agent, so we still don't know if the access comes from a crawler.

@fgiunchedi @mmodell got a sec sometime to discuss this? Here's a quick summary:

@MacFan4000 we doin't use php-luasandbox from sury. We use it from debian's official repo. It seems php-luasandbox is incompatible with php 7.2+ from when i tested it failed to find the luasandbox class.

I'm for keeping that text because:

• the user may be checking another page and then want to come back to the article and post it
• the case may exist on the page the user is on ATM
• the user may have forgotten to post it

@Jdforrester-WMF Is this ready to be marked Resolved?

Thanks for explanation. I expected that if namespace is not specified, API would not filter results by namespace.

• check if everything is OK with the new setting, a grace period
• after the grace period, delete VMs
• update docs: https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Admin/Services

Agree with high priority. Tagging with our backlog so we can discuss how to triage properly

I'd agree that this is not required for SVG Translate. Is there a task to create the log file you describe?