Mentioned in SAL (#wikimedia-operations) [2021-02-23T14:41:58Z] <otto@deploy1001> Synchronized wmf-config/InitialiseSettings.php: Migrate SpecialMuteSubmit to EventGate on all wikis - T268517 (duration: 00m 58s)

@Pchelolo are you working on this?

Mentioned in SAL (#wikimedia-operations) [2021-02-23T14:40:54Z] <otto@deploy1001> sync-file aborted: Migrate SpecialMuteSubmit to EventGate on all wikis - T268517 (duration: 00m 05s)

Change 666366 merged by Ottomata:
[operations/mediawiki-config@master] Migrate SpecialMuteSubmit to EventGate on all wikis

Change 666366 had a related patch set uploaded (by Ottomata; owner: Ottomata):
[operations/mediawiki-config@master] Migrate SpecialMuteSubmit to EventGate on all wikis

I can no longer reproduce the bugs in the description.

Status: ✅ PASS
Environment: enwiki
OS: macOS Big Sur
Browser: Chrome
Device: MBP
Emulated Device: NA

@Nikerabbit Sounds like a good plan.

In T274488#6852612, @Volans wrote:

Ok, if we go with ms-be1034 as hostname and we kept the disks, those are my thoughts:

• BIOS settings, set the management IP to 10.65.4.90 (ms-be1034.mgmt.eqiad.wmnet IP)
• HW RAID configuration in BIOS: double check it's the same of ms-be1034, the correct one that accepts the disks as is.
  • Could it complain that the disk IDs got changed?
• Update Puppet repo's MAC address for ms-be1034.eqiad.wmnet
• Let's use ms-be1034's device in Netbox: https://netbox.wikimedia.org/dcim/devices/1537/
• Decide which Serial Number, Asset Tag, Procurement Ticket and Purchase date to use in Netbox (ms-be1017 vs ms-be1034)
  • Maybe is more correct to set the values to those of the chassis (ms-be1017) as we just kept the disks of ms-be1034?
• Add to the comment field in Netbox the values in above point of the device that was discarded so that we keep them around.

@fgiunchedi do you plan to reimage it? If not we'll need to run a Netbox script after Puppet has run successfully. Not 100% if anything needs to be changed on the host, maybe nothing.

Depends on T275501

@aaron Please take a look and advise.

Draft for WMF https://docs.google.com/document/d/1a4ZISy2Vh0XHFRy3GefC9Qlzhq9xpGxRWa5vqZXBl4g/edit#heading=h.ppnulti1h3n7

Change 666364 merged by jenkins-bot:
[mediawiki/extensions/MassMessage@master] Remove mandatory line separator between page content and message

Looks good, resolving!

Not sure yet what's going on, but here's what I found so far:

Change 666322 merged by jenkins-bot:
[operations/software/cumin@master] integration tests: add undeduplicated output test

Status: ✅ PASS
Environment: hewiki
OS: macOS Big Sur
Browser: Chrome
Device: MBP
Emulated Device: NA

Context: T261125: Allow domain wikibooks.org from wdqs mwapi service was resolved by allowing calls to “any site that could be a sitelink”, but wikisource.org couldn’t be used for sitelinks at that time; it only became supported earlier today (T138332).

I thought about this and I think we should leave table creation to the last moment. It's fast, schema changes in production are a hassle, and the recommendation caching logic is complicated, so let's wait until it passed product review on beta.

Hmm, so I think that a new project + a herald rule to add always the SRE-tools tag should do the trick then.

In T132308#6335481, @Aklapper wrote:

In T132308#3305898, @mobrovac wrote:

The patch relaxing date validation is now live on all projects. It incorporates some of the suggestions outlined in this task, so please test it. Setting the task as stalled until further input.

Resetting task status as three years should have been enough time to provide further input (and as tasks should not be stalled forever).

Change 666180 merged by jenkins-bot:
[mediawiki/extensions/SecurePoll@master] Remove deprecated methods from ActionPage.php

Change 656452 merged by jenkins-bot:
[mediawiki/extensions/WikibaseLexeme@master] Update getStatementGuidParser() call

@Pchelolo Is there anything for us to do? Put it on Watching for now

@Eileenmcnaughton it's now up to $671k but I'm unsure of what is missing.

I am testing something on an-test-worker1002, but the next step is to merge the change to enforce uid/gid for Buster nodes and see how the reimages go. Before that, we need to manually fix these hosts:

Tags are projects are project tags.
Milestone could work but do see the "warnings" section first. Or Herald rule if all tasks tagged with #Spicerack should also be tagged with #SRE-Tools.

Change 666347 merged by Muehlenhoff:
[operations/puppet@production] Set a symlink for the host keytab

Ok, if we go with ms-be1034 as hostname and we kept the disks, those are my thoughts:

Change 664886 merged by jenkins-bot:
[mediawiki/core@master] Force unique ids for cloner-generated elements

Status: ✅ PASS
Environment: cswiki
OS: Windows 10 (Browserstack)
Browser: Firefox
Device: MBP
Emulated Device: NA

In T275453#6852591, @holger.knust wrote:

It looks like alt wiki was created. Are there any concerns about the state of the wiki?

Change 666364 had a related patch set uploaded (by Nikerabbit; owner: Nikerabbit):
[mediawiki/extensions/MassMessage@master] Remove mandatory line separator between page content and message

It looks like alt wiki was created. Are there any concerns about the state of the wiki?

Too vague to be actionable, also we're already doing this as part of other tasks.

Yup: https://en.wiktionary.org/wiki/Wiktionary:News_for_editors

Looked into this a bit, for our purposes the existing endpoint_checker does what we need.

The code currently is $pageContent . "\n\n----\n\n" . $message. I'm thinking I'm leaving just \n\n so that the message starts on its own line in the rendered text. Otherwise you would have to manually add empty lines in beginning of the message. This does mean that if you want, for example, to have the signature on the same line as page content, you cannot do it. But I guess this is less of an issue that accidentally having them on the same line.

Script wmf-auto-reimage was launched by elukey on cumin1001.eqiad.wmnet for hosts:

an-test-worker1002.eqiad.wmnet

The log can be found in /var/log/wmf-auto-reimage/202102231401_elukey_6277_an-test-worker1002_eqiad_wmnet.log.

Where possible, it'd be nice to stick with the existing mediawiki event conventions. See also https://schema.wikimedia.org/#!//primary/jsonschema/fragment/mediawiki. I'll also comment in google doc. :)

Or maybe not xd

Tasks in subprojects will not show up on the workboard of the parent project.

Maybe as a subproject? According to the wiiki (https://www.mediawiki.org/wiki/Phabricator/Project_management#Parent_Projects,_Subprojects_and_Milestones) namespaced projects are allowed, but not sure if that's only for 'umbrella' projects.

At the German Wikivoyage, Reading preferences (Enable page previews (quick previews of a topic while reading a page)) are not available.

Here's my current "draft" of what the schema could look like:
(Once again, the idea is that whenever the user submits a single Image Recommendation item, we send an event to a new Eventlogging table that we'll use for this experiment.)

I have the same issue on es.wiki. I am unable to add this user to the confirmed users user group because it does not appear. https://es.wikipedia.org/wiki/Especial:PermisosUsuarios/Tlakwilo

Yes, or just remove it.

What are the options here in terms of tag vs project? Is a tag also a project anyway? Can all the tasks tagged show up in the existing SRE-tools workboard?