- Mentioned Here
- T49930: [Epic] Allow accessing data from a Wikidata item not connected to the current page - arbitrary access
T87009: StorageException from line 34 of TitleFactory.php: No page found for ID 1305
T87010: EntityUsage not cleaned up when deleting pages in client
T87026: testwikidata entries not appearing in recent changes or watchlist on test.wikipedia
appears to be working now :)
https://test.wikipedia.org/wiki/Kitten_on_arbitrary_page (and the wbc_entity_usage table is updated)
and correctly not working yet on test2:
when I run dispatch changes for test.wikidata, I see https://test.wikipedia.org/wiki/Kitten get updated but not https://test.wikipedia.org/wiki/Kitten_on_arbitrary_page (assume this is still a @todo to get that to work)
I also don't see Wikidata entries in recent changes or watchlist on test.wikipedia, but do see them on my local dev wiki (with usage tracking enabled) and see them on test2. needs further investigation why changes are not appearing on test.wikipedia, but otherwise seems to work ok now.
Are these the issues referenced at https://wikitech.wikimedia.org/w/index.php?title=Deployments&diff=141185&oldid=141045 ?
(Please link blocking bugs/tracking bugs in the future, since you have them :) )
Jan 21st (Wed) is All Hands for WMF (Wed and Thurs next week). Monday is a holiday for the US. So...
We won't be running the train next week but will allow one-off low-impact things on Tuesday. No deploys (except really important) on Wed/Thurs due to all of ops and releng etc will be doing All Hands things.
Week of 19th
- No MediaWiki train deploy due to WMF All Hands
- No deploys Mon/Wed/Thurs/Fri
- SWAT/etc on Tues OK
Week of 27th
- No MediaWiki train deploy due to MediaWiki Dev Summit
- SWAT all week as normal
- no other deploys Mon/Tuesday
i actually don't know how long populating the table will take. we might go ahead and add it earlier and start the script earlier in the day. idk what time.
then the enabling should be fairly quick and easy. (already did it for test.*)
@Tnegrin for Wikidata itself, should be no difference since arbitrary access is already enabled there. (e.g. access properties and items on any wiki page, such as list of properties)
usage tracking provides internal tracking of where an item is used on which wiki page, and then will allow us to automatically purge/update that wiki page when the item changes. (not sure how much automatic purging we will already have at this point, though)
we then hope to enable on commons next, but not sure when... commons does not have arbitrary access yet, so they will get usage tracking + arbitrary access which is a bigger deal.
the internal tracking will definitely allow us to have more stats on what is used, how much, where, etc.
@Manybubbles explained this to Bryan and I, and I'm going to attempt to explain this as simply as I can:
This is step 1 of 3(?) toward arbitrary
list item transclusion (T49930) on Wikipedia et all. This aspect of it is basically the "related changes" bit that allows for proper purging (but doesn't actually do it).