We mived to pytest!

The old servera have been shut down a while ago and things seem to work fine so I'm going to assume the last two parts of the issue didn't warrant any changes.

This seems to have been fixed in 2023. Reopen if it occurs again.

There are additional occcurences in the tools/ directory (ranking, wlmlast, gallery-all). But those are already broken from before (neither using the actor or the linktarget tables). Worth having an active decision whether to keep and maintain or drop these tools.

Quixk code search identifies these two:

Thanks @Xqt. I appologise for having missed those changes. Will investigate if that solves it.

Requesting a different mechanism for setting user agent at T422276: Allow setting user agent without user-config

This now works! Great work @Akoopal

Wondering if this is the right overarching task. But i think T422276: Allow setting user agent without user-config might be related to this one as well.

I actually think min_row_ratio per country might be overkill. A sutiablr defualt and a force flag should be enough.

The merged patch mickes the Pywikibot features which connect to live sites and adds an additional block to prevent any future tests from being able to connect to the network

https://commons.wikimedia.org/wiki/Commons:Monuments_database/Missing_IDs is now up and running

These are now linked! from https://heritage.toolforge.org/

Dumping the research here.

This is now being published at https://commons.wikimedia.org/wiki/Commons:Monuments_database/Duplicate_IDs!

@JeanFred this one!

Cannot reproduce this error right now. File is currently not being added to the list. Feel free to re-open if you have another example.

I'm going to close this as declined. Feel free to reopen if someone else want to take the lead on the data provider side

Fixed!

Some expectation management here. I don't believe this issue is the cause for the recent downtime.

Hoping I picked the right Wikibase component, appologies if I didn't.

Did a blank edit to the page and can confirm that both are now sorted under P

In T299824#10890115, @Lokal_Profil wrote:

@Tpt will you have an opportunity to take a look at the patch? All I did was to drop a parameter in the parserOutput->addCategory call.

@Tpt will you have an opportunity to take a look at the patch? All I did was to drop a parameter in the parserOutput->addCategory call.

Dug into this again. The culprit is L580 of includes/Index/IndexContentHandler.php which accidentally sets the sort key to the category title. In my local environment I could fix this easily.

This likely falls under T335067: Epic: Wikidata Query Service stabilization