Injecting recent changes from Wikidata is currently disabled on Commons:
'wmgWikibaseClientInjectRecentChanges' => [ 'default' => true, 'commonswiki' => false, // T171027 'testcommonswiki' => false, // T171027 ],
With T177707 and T173194 being solved it should be ok to re-enable Wikidata Recent Changes integration on Commons. Let's reenable it and monitor if everything is ok.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T90435 [Epic] Wikidata watchlist improvements (client) | |||
| Open | None | T91192 Show new versions of files (and possibly separately description changes) made on WikimediaCommons on the Watchlist | |||
| Resolved | PRODUCTION ERROR | Bawolff | T171027 "Read timeout is reached" DBQueryError when trying to load specific users' watchlists (with +1000 articles) on several wikis | ||
| Stalled | None | T179010 [C-DIS][SW] Re-enable Wikidata Recent Changes integration on Commons |
Thanks for the heads up.
When do you plan to re-enable this?
How are you going to monitor it?
Not really… T173194: Module:Wikidata label should use mw.wikibase.label and mw.wikibase.sitelink alone should more than half the number of changes happening (as it reduced the number of all usages on commons by more than 50%).
T177707: don't dispatch changes to all affected pages for highly used items has probably even bigger impact, but I can't really put a finger on this right now (given the relevant data is no longer there). This means we wont ever create more than 20 RC rows for a single Wikidata change.
We would like to do this at 12:00 UTC tomorrow.
I would monitor the rows written and replag graphs for s4 tomorrow, as well as the number of RC rows.
Given the issues this have caused, I would prefer if it gets enabled on Monday or so.
Why? Because it might have a couple of days to see if this doesn't cause issues this time. And two days means the weekend and no time to react.
No it is still waiting on Marius.
Marius: I'll put int in the next sprint and then Amir can handle it if you don't have time.
I think we can do this now, nothing technically stopping us from our side.
Just need an OK from product / the community, and then to also give DBAs a little heads up per T179010#3710181 (@Marostegui )
It is not central to our current hike, but in the vicinity. So let's add it for visibility
Personally I have no problem, but bear in mind that it could show a *lot* of changes for categories, since Wikidata info is used so much there - and in multiple languages. I'm not sure how it would affect watchlisted file pages via SDC. If it's turned back on, definitely do so early in the week so there's plenty of time to check for issues before the weekend!