We've deployed a fix and this should be resolved in the next half an hour.

Makes sense to me

We could look into changing $wgPageImagesLeadSectionOnly

@Paladox has made changes and it seems to have solved the issues.

Nothing is exploding although commands/sec (and misses) are still elevated

Redis was restarted. That may help.

Performance is much worse last day, wiki creations are fairly critical. Declaring UBN.

In T10963#220963, @AmandaCath wrote:

@Naggieka what do you mean by "fastdeleting" pages?

[7b0acdd4a02b1d2c8750e711] 2023-06-26 13:27:31: 类型“Wikimedia\Rdbms\DBQueryError”的致命异常

Cool URLs shouldn't change so keeping a redirect imo is a good idea. And +1 to CF. I have both my personal domains with Cloudflare (also using CF pages with them).

In T10943#220805, @Dmehus wrote:

@Void What did you need done on the listed Discord servers? Do you just need the Discord server administrator to re-add the new relay bot to the Discord server, or to DM you their new token? Pokey is the Discord server administrator and bureaucrat on buffalonaswiki. Not sure what his wiki username is, but on IRC he is pokey@spikeyCactus/hoosky. :)

Agent Isai would be the Discord server administrator for the other three IRC channels, I think. I know he's founder on the IRC side.

The CVT feed bot is also down

In T10910#220491, @Bonbonyoshi wrote:

Hey, sorry if I'm acting impatient with this, but could anyone tell me if this is/would be allowed to go through? Thanks.

A lot of SRE are on a break or have resigned.

In T10915#220214, @Universal_Omega wrote:

https://www.mediawiki.org/wiki/Extension:ParserMigration

I've spoken to the parsoid team to see what's likely to happen.

https://github.com/miraheze/mw-config/pull/5242 should be merged after we're on 1.40

In T10915#220073, @Original_Authority wrote:

Can someone clarify what "completely broken" means? I'm experiencing no such issue running the master branch on 1.41-wmf-11?

I'm going to do some research for you on what it will look like for non-wikimedia wikis.

Apologies for the issues. The commit that caused has been reverted.

Similar report for weirdcorecity.miraheze.org

IPInfo is most definitely going to expose private data once IP Masking starts but it's minimal (geographic location and ISP). The WMF are asking users to agree not to share the data but no full NDA needs signing.

Removing a protection level is not a steward matter. It's most definately within the scope of SRE.

Upgrading to phorge is a normal phab upgrade with 2 extra steps. There is a guide that details it. I've done it for fossbots and it took 15 minutes.

Script ran, leaving open for IR

Assigning to Reception123 to see why the l10n deploy didn’t log and confirm that the Special:Upload message was removed.

In T10717#216495, @Void wrote:

Ran a few tests wiki setContainersAccess.php and it looks like the script restores the containers without damaging any of the files. I think, after testing with meta and commons, that it is completely safe to run it against all wikis to restore everything without waiting on the containers to repopulate on their own.

In T10449#211027, @Asquidbro wrote:

@OrangeStar any updates pls?)

The certificate provided is not valid.

This has been done on abbreviationswiki. Please investigate asap.

Thank you for the report. We will track this on T10305: SSL for custom domain: <insert subdomain>.miraheze.org.

Passing to MW team to carry out the email change.

Please link the file to the task. There should be an attach button. (Task is public so ensure no private content from wiki first).

In T9712#196193, @John wrote:

"Was force pushed without waiting for CI by John @ 19:56"

It wasn't forced pushed - it was committed?

Clarification: CI there to point out exactly this was bypassed by merging without a PR and then when post merged failed completely ignored for about 10 minutes

Advised on discord to use ManageWiki

In T9545#195349, @The_real_kbos_Cuddly_Rainbow_Guardian wrote:

this just happened when i was looking at my global account info

Please open a new task.

In T9457#194383, @Ugochimobi wrote:

“In this document, when we say “Wikimedia Cloud Services”, we mean content or services hosted on wikitech.wikimedia.org, wmflabs.org, or a subdomain of wmflabs.org.”
According to this statement, Does the Wikitech ToU not cover wma.wmcloud.org?

In T9601#193959, @John wrote:

syslog suggests the networking service on cloud10 was restarted

I don't believe a human did it. Surely it shouldn't randomly restart.

Hopefully

We're sorry for this.

Reported nearly a year ago at https://phabricator.wikimedia.org/T287725

Deprecated: Use of BaseTemplate::getAfterPortlet was deprecated in MediaWiki 1.35. [Called from GreyStuffTemplate::getPortlet in /data/project/skins/public_html/skins/GreyStuff/includes/GreyStuffTemplate.php at line 222] in /data/project/skins/public_html/includes/debug/MWDebug.php on line 377

This causes a flash of the screen on skinswiki so -1 and I expect a decline.

_construct_l10n_command was added with https://github.com/miraheze/puppet/pull/2456/commits/ef8aaa8cf37f335dfa64f4fbb3588bd802626202 and will be merged with v4

Side note: we don't install extensions using the distributor anywat

Already available. We don't install it globally. Please use loginwiki.

https://github.com/miraheze/puppet/pull/2687 for what I can see in puppet

https://github.com/miraheze/puppet/pull/2687 for what I can see in puppet

There is no concept of an owner.

XMLs can now be requested though using ImportDump on meta. Please see the new imports guidance.

Please attach the file

Yes

Please try again if you can't use the request page

Afaik no

I can.

You just need to enable TemplateStyles

We also can't see your screenshot. It needs attaching to the task.

Hi, You can now use the RequestImportDump page. Please try using that to speed up the process!

There's only no native support for multiple wikis so this would be 6GB memory needed and a fair bit of sysadmin time.

Blazegraph is far too unstable. This would be a massive hog on resources.

Thanks for the report. Reception123 restarted and I forgot to close but it's back now.

Thanks @Untropicalisland: can you confirm your Firefox and OS version either here or on the Firefox ticket linked?

OAuth: already installed.
Elasticsearch: not available and won't be for some time.

Yes

Raised this at https://bugzilla.mozilla.org/show_bug.cgi?id=1774861 - please disable Total Cookie Protection if it's enabled.