Sorry, I've been on vacation the last two weeks. You are right, the jobs are no longer needed.

In Version two we have a data issues special page where we want to be able to filter all violations by constraint_type_qid, so we think, an index makes sense.

List of all properties with constraints on test.wikidata.org

We have created some items and properties to provide you some data to play with. The items we recommend you to perform constraint checks against on our special page are:

This is probably because of the renaming of the repos. The name "WikidataQuality" was considered bad since the extenstions are not specific to Wikidata. Therefore, the Wikidata*-repos aren't used anymore. Instead of "Wikidata", it is "Wikibase" now.

How do you need this messages? In which form and where?

We are working together with Amir (Ladsgroup) to get this done.

Could you be so kind and clarify the blocking issues for the other two extensions? For Constraints we have seen only one open ticket (T101467), for which we have uploaded a fix.
Same for the Quality extension. Only one blocking task for which we have uploaded some patches. I'm not sure if we can close it on our own or if you could have another look at it?

Please reopen if the removement of the RegEx check does not solve this problem.

We removed the check for the regular expression in the version that should be deployed and are working on a fix for the next version. (https://gerrit.wikimedia.org/r/#/c/218857/ ).
Can we close this ticket?

Great idea at all. Since we are already parsing all constraints with their parameters, it should be really for us to create this list. I will try to bring it to the office today.

We read about this and understand it's problematic, but we still have no idea how to fix this issue. For concerns about the runtime we could add a timeout which would lead in the worstcase to a false negative, but about the exploit-stuff-case...

That's also what is happening for me. Is this the way it should work? I was expecting this http://wbdoc.wmflabs.org/d3/da4/classWikibase_1_1DataModel_1_1Statement_1_1Statement.html to be part of the result list. And I am almost certainly sure that it worked a few weeks ago.