In T167221#3445181, @mmodell wrote:

There is no reason for you to visit the quickstart setup guide. That page is for administrators.

We should block that URL for the sake of avoiding people DOSing that url.

Make shortpages exclude file: namespace on commons could be an option no?

Buttons are now grayed out for user w/o proper permissions.
See attached screenshot:

1:53 PM <ebernhardson> depending on which thing is sending to logstash ... for example amir started sending ores logs to logstash with https://gerrit.wikimedia.org/r/#/c/321096/11/modules/service/manifests/uwsgi.pp
1:53 PM <ebernhardson> basically just stuffs python logging on a socket that logstash reads

Merged sorry for late update

I mean the oauth process is the same regardless what wmf wiki is used, and is (IIRC) i18n'd so besides unfamiliarity why should this need to be changed?

@Halfak are we still working on this or am I okay to close this?

[05:13]<mutante> celery seems to mean it's an analytics thing
[05:13]<mutante> is this about getting into stats?
[05:13]<mutante> ＋https://wikitech.wikimedia.org/wiki/Wikimetrics， ?
[05:13]<mutante> eh, gettin data OUT of stats?
[05:14]<mutante> maybe it's a question for #wikimedia-analytics if they run celerey ?
[05:14]<mutante> the word "celery" doesnt appear in site.pp either

patch is there still awaiting merge...

In T169979#3416969, @Dzahn wrote:

Do you mean running a script on a maintenance server?

If that is possible to do sometime, yes if i need to be there let me know and i will show up :)

IIRC ops have to run a script to upsate the interwiki map therefore adding the tag

Resolved already. Reopen if im incorrect

any news?

In T168014#3379263, @RobH wrote:

I'm removing the Operations and Ops-Access-Requests tags, so this doesn't show in clinic duty triage, since its no longer an active request. I'd have declined it, but since its on two other projects, requested tag removal over closing task was requested. (Either works!)

In T168014#3368117, @RobH wrote:

It seems this is awaiting followup from @Zppix to work with @Halfak (as the employee who sponsored his access) to get the following steps:

• a comment of approval from one Wikimedia Foundation manager (usually the manager of an employee supporting you), so e.g. Dario
• sign off by a C-level staff of the Wikimedia Foundation
• @Zppix works with @RStallman-legalteam to sign and file an NDA with WMF Legal

I've gathered that from above comments from @MoritzMuehlenhoff.

Please use phab-01.wmflabs.org to test phabricator!

https://phabricator.wikimedia.org/file/info/PHID-FILE-g3doxzwaur6pzftyzt65/

In T168142#3357514, @Framawiki wrote:

We probably need to block OAuth for WP Zero, OAuth process is the key to access to phab and other tools.

https://phabricator.wikimedia.org/file/info/PHID-FILE-o7aq7quzr2upy56qmrl3/

In T168087#3355721, @Jaredzimmerman wrote:

I"m not sure how to make it more clear… the favicon is not HiDPI compatible, meaning it is blurry on high definition screens. Take a look at the 3rd link i included on how to prepare retina favicons.

What is this task referring to exactly? The description and title are very vague. Please look at https://www.mediawiki.org/wiki/Special:MyLanguage/How_to_report_a_bug and update this task accordingly please.

@Aklapper good point when i glanced through the description provided it looked like a tool of sorts but now reading it in full I see its not needed therefore im redacting that comment. sorry for the inconvience.

In T167061#3353401, @Halfak wrote:

Updated wikilabels with bugfix and tested by getting the target error message and then labeling some edits. Declaring victory.

I talked with Halfak he agrees with going with, grafanna, however he wants the Graphite metrics for changeprop therefore i submitted a request for myself to be granted access. I will contiune investigating as much as possible to find a way to prevent this from occouring completely. I will also see if I can find if this has happened before and it was just never noticed, it appears however scb1001 is the only host that will be affected, I wonder if we need to distrbute ores throughout the entire scb cluster and load balance. If thats impossible then find a way to make sure scb1001 isnt the only instance that ores can depend on to run properly. I will also talk to pdrender's maintainers/services to see what we can do to limit interaction server resource wise between ores and them. If anyone has any relevent info on this incident that isnt already known please feel free to add it, or if you have suggestions. Thanks!