Hi DBA, input requested please :)
Here's what it looks like now:
Related: T70689: User Preference's default options/values should be automatically marked in the special page itself, which mentions this problem.
Sun, Jun 23
Sat, Jun 22
Fri, Jun 21
Here's the PHP coverage report: https://doc.wikimedia.org/cover/mediawiki-services-parsoid/
Unclear whether this needs fixing at all...
Thu, Jun 20
@Xaosflux it's already been fixed, we're just waiting on deployment to resume.
# Intentionally ignore special_extensions because they're special return ['mediawiki/' + name for name in conf['extensions']]
Actually, I think something else might be going wrong here...the notification *should* include the section title. EchoEditUserTalkPresentationModel has a bunch of stuff for the section title, but I don't see it in the primary URL. My guess is that DiscussionParser isn't grabbing it correctly.
Pharos bugged me about this again in person today.
This caused a lot of frustration for me today, when I was trying to help someone determine why their new article wasn't showing up in search indexes. Eventually I looked at the HTML source of the page and saw the noindex tag.
Wed, Jun 19
I ran into the problem as well.
It wasn't a local patch, it was just that environment variables like this are normally injected by *zuul* not *jjb*. And the phan and seccheck jobs do share some common config, which was prematurely removed.
Tue, Jun 18
Submitted patches for all of https://codesearch.wmflabs.org/search/?q=Wikibase%2Ftests%2Fphan&i=nope&files=&repos=
WikibaseCirrusSearch shouldn't be importing .phan/stubs for analysis...
Mon, Jun 17
The bandaid that's in place should be good enough to prevent codesearch users from seeing any problems, though we do need to properly fix the ED API.
Fri, Jun 14
Thu, Jun 13
If we change extension.json to:
Sorry for cookie licking, I haven't worked on this since October :(
Wed, Jun 12
I think the schema change also needs to be made on private wikis too.
(Uh, I forgot to press submit on my comment, sorry.)
This would effectively just kill the LTS effort if we can't adequately test releases and force people who care into using proprietary CI systems.
https://wikitech.wikimedia.org/wiki/Releases.wikimedia.org#GPG_operations has the instructions to regenerate the key. Based on what happened last time the key expired, I believe someone from the Operations team will need to take care of that.