Going to close this in favour of what is being done in T248308
Going to mark this as resolved for now as the investigation and initial fixing of holes was done.
The issue is now much smaller and followups already exist that would totally eliminate it.
Until then the store will slowly keep itself in check
That would probably be T247704: Use lock manager for the new term store deletions
So, these still happen, but at a much lower rate.
This is probably still something that we would like to iron out and that we would probably tackle with some locks for updating entities higher up in the application (not in sql).
I will poke the new asignee
We are investigating if this tool is needed at all or if we can just delete it
I'm just going to leave this to be tackled by federated properties..
Moving to the iteration so I keep my eye on it and investigate throughout this train rollout..
So, diffs actually load fine that relate to the revision. but the revision can not render (or seemingly save).
I also get errors on beta while trying to use wbeditentity to make an edit adding lots of terms.
I have prepared test wikidata with a revision that breaks beta currently https://test.wikidata.org/w/index.php?title=Q64&action=history so we can see what happens as the train rolls forward.
Now going to look at recent code changes to see if I spot anything.
Something has obviously changed, and it relates to the number of terms that have been added to the item in https://wikidata.beta.wmflabs.org/w/index.php?title=Q64&oldid=1161819
Viewing these revisions obviously used to work as the item has been editing many times since the creation of that revision without problem.
I wonder if this is a core of Wikibase change, probably something relating to lots of Language objects.
Interestingly it just loaded for a first time now for me!
One notable thing that did change with the deployment of this config (the repo bit) was the result of the wbsearchentities api which now lists "wikidata" as the "repository" instead of local always.
Mon, Mar 30
From task breakdown:
- update regularly, either using cron or through a web hook on every merge
- set up, configure and maintain everything via ansible
- ansible config file to be version-controlled in a federated-properties config folder of the Wikibase git repo
- Everything i.e. docker container setup and mounting docker volumes, code updates from git, setting up the automated updated ("cron")