Update: The wikibase-cli author resolved the problem with a new version of his toolkit, see https://github.com/maxlath/wikibase-cli/issues/150

Seeing this too for a few weeks now. The fail rate is 10-20% on average, up to one third of added statements. I'm using wikibase-cli, in one thread, nothing else.

Nice coincidence @Lydia_Pintscher , see also https://www.wikidata.org/wiki/Wikidata:Project_chat#referencing_specific_statements

Very helpful, thanks again.

That explains it, thanks. Would it be odd to run a (low key) worker in a kubernetes box?

There is now an experimental query service at https://adhs-wde.toolforge.org/sparql that has a subset of all EntitySchemas. The default query shows that the ShExC code is embedded in the RDF as a rdfs:comment and can so it can be queried too. The next milestone is to load from the WD database instead of static files.

Thanks!

I'm realizing right now that changing Extension:EntitySchema to use a triplestore would make a general handling of RDF data possible, if there were further need for additional types.

Reevaluation might be easier after having a dedicated triplestore available, please see T271065.

Thanks, that would be a practical solution.

For the wikibase-cli toolkit I opened https://github.com/maxlath/wikibase-cli/issues/120

Can we please have any feedback on this? I cannot believe the importance of this ticket is judged as low. This is basic functionality that does not work.

See https://www.wikidata.org/wiki/Property_talk:P492. So I think it can be closed here.

I see, thanks. I will discuss adding a complex single value constraint to relevant properties ("OMIM ID" mostly), removing the simple one at the same time.

From the help this should work:

Please delete/redirect them on WDQS.

Please also include the items from https://www.wikidata.org/wiki/Wikidata:Contact_the_development_team#query_not_in_sync