As far as I can tell, this should now be good to go.

Adding a two week due date as agreed in the retro, since the task that this waiting on is currently on top of the prioritized product column: T260073

Added (default?) 2 week due date to see if https://gerrit.wikimedia.org/r/c/mediawiki/core/+/626854 is merged, then we can proceed as described above (T205094#6460185).

Will review the patch. Let's see if I also manage to create one for the other callers mentioned in the commit message

I think this can now be closed:

I think this can now be closed:

This has been done in #159.

Great! I'll make a pull request for removing it. 👍

Thank you for your thorough research. That means we can effectively drop property suggester? Not having to do that extra network request should speed some things up.

I'm not sure what this task is referring to. I looked through our current features and it seems there is barely any to which the number of statements is relevant in the first place.

I got started with this earlier, unfortunately, phabricator is not yet adding backlinks from github: https://github.com/wikimedia/articlequality/pull/149

This is not a Data Bridge bug. It is a bug in the new release of the OOJS-UI library and our browser tests merely caught that bug. Good thing that we have them.

Ugh, always on a Friday evening. Looking into it a bit and also coordinating with this weeks IM @Addshore

Mh, true. I can't reproduce it with closing/restoring a tab or session. Guess we just have to accept it as a mystery for now. Moving to verification for @Lydia_Pintscher.

Added all tasks to https://grafana.wikimedia.org/d/pVG7xcAZz/wikidata-bridge.

When this is deployed with the next train, then we should check whether T260384 still occurs. (logstash)

Looking at https://doc.wikimedia.org/Wikibase/master/php/md_docs_topics_options.html#autotoc_md256, I'm still not sure about this.

Can confirm that it no longer happens on https://ca.wikipedia.org/wiki/Berlín 🙌

Since this is only happening on commons, I'm adding the respective projects.

Seems to be related to our federated properties hike

Can confirm it on beta. Will remove the reference to a production source map.

I'm somewhat stuck with adding the test in this patch: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikibase/+/621305
The trouble is that I can't think of a way to actually test that the mock is adjusted that wouldn't also be green if it weren't.

moving back to doing for the testcase

I already adjusted it and I thought/intended to set the default dashboard time frame to "the last 7 days" as that would seem more useful anyway. Not sure why it shows you the last hours again?

In T260532#6393975, @Lucas_Werkmeister_WMDE wrote:

I think I’ve fixed the Data Types dashboard on the existing panel now, other panels TBD later.

Also, we should double-check the existing panel as there should be some data displayed by now, even if it comes just from us playing around with it on cawiki.

In T259783#6390525, @Ladsgroup wrote:

Is this done?

A bit already exists: https://grafana.wikimedia.org/d/pVG7xcAZz/wikidata-bridge

This sounds suspiciously like it is caused by T259783: LanguageFallbackChain does not end in 'en' for language codes that are not a valid format, which should hopefully be done very soon. Though, I'm a bit confused as to why it only started with the last train 🤔

Also, I think this is still causes rare-ish production errors. While they may not have a big impact, they do show up in our logs. Confusingly, they only show up since the last train on August 12th, not since the week before as I would have expected: T260384: Wikimedia\Rdbms\Database::makeList: empty input for field wbxl_language

This is in practice waiting on some other ticket: T260073: Wikibase namespace names cannot be translated (anymore?)

As far as I can tell, all associated patches have been either merged or abandoned.

These changes need to be announced before they can be merged

As far as I can tell, all associated patches have been either merged or abandoned.

As far as I can tell, all associated patches have been either merged or abandoned.

I added a few lines about the Grafana alerts to https://wikitech.wikimedia.org/wiki/WMDE/Wikidata/Alerts. Would be nice if someone could check that they make sense.

This is not technically a Regression as it was always broken for "languages" like ⧼Lang⧽ or %E2%A7%BCLang%E2%A7%BD . However, since we have validation for our TermLanguageFallbackChain, this problem/bug has become more apparent, because now the chain can be empty whereas before it at least contained the invalid interface language.

Thank you for pointing me to this ticket. This ticket should indeed be mostly done when T259783: LanguageFallbackChain does not end in 'en' for language codes that are not a valid format is done. However, getLanguagesOrderedByFallbackChain will semantically change from always at least including the interface language to always including at least the content language. Unfortunately, I missed that during T256405: Investigate where and how \Wikibase\Lib\LanguageFallbackChain is used. And I'm not sure whether that is a problem, because I do not know the domain enough. So, I think this ticket here has its reason to stay open to make sure that is taken care of and not forgotten.

Risks, threats, challenges identified

Seems fixed to me 🙌

This seems to be blocking the merging of the patch 618703 for the current UBN T259744 and maybe T259745, thus triaging this as Unbreak Now! as well.

Adding Pablo as the IM in charge for the ongoing incident, Lydia as the PM for Wikidata, Thiemo as the dev that provided the patch and Adam as the one in charge of tech tickets.

We still need to confirm whether abstract schema _changes_ is actually already available. The docs indicate that it is not done yet, but they might just be outdated.

• Consider naming schema
• consider sorting files into subdirectories by years or tables or MediaWiki versions
  • MediaWiki core seems to partially sort their changes into subdirectories by database driver, see :https://gerrit.wikimedia.org/r/c/mediawiki/core/+/473601
    • I'm skeptical whether this way is the best approach for Wikibase or whether we should keep representing that as part of the naming scheme, similar to what we have now.
• investigate which parts of DatabaseSchemaUpdater can maybe be deleted because they are very old
• we probably can mark everything for deletion older than MediaWiki 1.31