August 12th. So this session already happened?

PHP makes limited breaking changes in minor releases. I already updated two MediaWiki extensions to avoid issues on PHP 8.1.

What about PHP 8.1 for MediaWiki 38? Can we expect it to work as well as MW 37 on PHP 8.0?

This causes problems for SAML auth. See https://phabricator.wikimedia.org/T246350 and https://www.mediawiki.org/w/index.php?title=Topic:W5nyw48nx1pc2lsy

Anyone found how to fix this yet?

This is kinda painful for anything outside of Wikibase that relies on this PHP code such as extensions or tools. Firstly there is no deprecation period, the breaking change just instantly happens. Secondly, and more painfully, the new alternative is only introduce at time of breaking change, making it super difficult to support both old and new Wikibase.

👎

@dcausse: will anything bad happen if the URL comparison that is currently failing is removed? And is that applicable to people running their own Wikibase?

👍

@dcausse is it realistic to expect this bug to be fixed by Wikimedia in the near future? Several institutuions that we are helping with Wikibase adoption are running into it.

I've added the description message: https://github.com/ProfessionalWiki/EDTF/blob/master/i18n/en.json#L2

@abi_ fantastic!

Thanks @Reedy. We now have message docs in qqq.json. Anything else that needs to happen?

We now have the messages in JSON format similar to MediaWiki: https://github.com/ProfessionalWiki/EDTF/tree/master/i18n

Thank you abi_! We will use the MediaWiki i18n JSON format.

The library now has GPL license and should be ready for TranslateWiki.

And is there some recommendation on what to do in PHP? Is there a standard implementation we can use? Is using something like https://packagist.org/packages/gettext/gettext recommended, or is it better if we create our own thin wrapper?

Is there an technical documentation on how to interface with TranslateWiki? I guess there should be message files in _some_ format at _some_ location, but am unsure if there are any restrictions, preferences or best practices we should be aware off.

Use cases for DNB:

Looks like this is a QuickStatement issue that is already tracked: https://github.com/magnusmanske/quickstatements/pull/1

After the latest fix the extensions/OAuth/maintenance/createOAuthConsumer.php script is running without error.

Props for the fast response!

In T248925#6672023, @Jdforrester-WMF wrote:

monolog/monolog 2.0.2 requires php ^7.2 -> your PHP version (8.0.0) does not satisfy that requirement

Fun.

Does anyone know to which degrees MW 1.35 and master run on PHP 8.0? (I understand there is no official support)

We put the data type in a new extension. In retrospect perhaps we should have done that right away.

Thanks @TheDJ! Fixed with https://github.com/JeroenDeDauw/Maps/commit/eab4fcaa969b7b284aaa1fc530f2b53a3fcf6f6a

I think there is wisdom in "less is more" and that talk pages do not make sense for all wikis. A clean way to disable them would be nice.

In theory it could call wfLoadExtension()

It'd be nice to replace mediawiki/mw-extension-registry-helper provides with something simpler while retaining automatic enabling of dependencies. Can an extension somehow enable other extensions that it depends on when it is enabled? (We'd make this optional so you can define things manually/explicitly for WMF wikis.)

Also seeing this issue

Is this on some roadmap?

+1

https://github.com/wmde/WikibaseDataModelServices/pull/219

Ready for review: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikibase/+/507954

One thing left in the maintenance script itself: support property id ranges. I will work on this today

I think something along these lines makes sense, please comment here: https://github.com/wmde/doctrine-term-store/pull/8/files

I am also not happy with this task, as again it specifies a solution, not an outcome. I much rather have "avoid expensive cleanup during the request to the degree this is possible" as acceptance criteria in the story.

We talked about this (two weeks ago?) and concluded there likely is no need to introduce anything in wikibase/term-store. I'm pretty annoyed with this task now since it specifies a solution rather than a problem that needs to be solved.

WikibaseImport contains a limited number of items and properties

https://www.mediawiki.org/wiki/Manual:Job_queue

This means we have to go with the "smart update using diff" approach, since otherwise we do not know which terms have been removed. Not clear to me it will make sense to do the cleanup in post-request, we might end up only delaying a few % of the cost. I suggest to first make it work on write and then see if we can gain a lot by moving stuff to a job.

I'm calling it a day. Current guess is that the tables are not created right because we are not using this setting in mediawiki/doctrine-connection.

There is some issues though. Some properties result in an error, and on re-run many of them do.

With https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikibase/+/501992/ the rebuilding works using the Doctrine Term Store.

@alaa_wmde what is the status of this?

AFAIK the script we currently have (https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikibase/+/505670) is sufficient for this task. It has continuation based on page id rather than property id. I figure that won't fly for items but likely is OK for properties. Do we need continuation at all for properties?

https://github.com/wmde/WikibaseDataModelServices/pull/216

We already did some of this while working on the property script: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikibase/+/505679

Yesterday while thinking about design stuff I randomly realized that we might not need a script like this. Can't we just use https://github.com/Wikidata/WikibaseImport to important a bunch of real entities? If that is too slow, then perhaps we can use https://github.com/JeroenDeDauw/Replicator to import JSON dumps.

https://github.com/wmde/WikibaseDataModelServices/pull/214

https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikibase/+/503331

Don't think it is a good idea to modify the existing RebuildTermSqlIndex code. We can just create a new script. The existing code has things in there we don't need, and still having the wb_terms specific thing around might be useful to various users.

@alaa_wmde is this done?