"Upper limit: 2" corresponds to the form field below named as "Upper limit of matching tests". There is no significant reason for it not to be exactly the same, I will make a note to make it identical.

Thank you @Etonkovidova, yeah these ones seem to be the same issue, and the errors were the ones we triggered yesterday while working on the issue.
Once https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikiLambda/+/1102919 is deployed we will be able to fix the object successfully.

Provided List with form, with Type and Language fields. The list renders objects that are missing Name in the given language. Input labels are not included in here for the problems described in my previous comments.

I've experimented a bit, and the list of objects by type that have no name in a given language is quite manageable:

The absence of Function name can be gathered from the labels table. However, the absence of input labels is something which isn't available anywhere.

Maybe repeat the 'mul' hack we have for Z60s to also put the ZID in as a mul alias?

All the stored ZObjects are in canonical form.

Additionally, although the use cases are not so common, this issue can also be replicated in our other instance of Codex Lookup, the ZObject selector.
For example, while using the language selector after expanding text to find the language of in the language of monolingual text/Z14404 function:

Setting the visibleItemLimit does help in avoiding the problem.

@egardner I can help with that.

Marked this as invalid as the issue came from a screenshot of a WIP. Fixed this as part of the ongoing patch: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikiLambda/+/1083137

This is a duplicate of https://phabricator.wikimedia.org/T377332
This was fixed and merged last week, so I believe the fix will go live soon. Thanks!

The codex team is working on a new component for these floating messages https://phabricator.wikimedia.org/T303612
We have been using cdx-message in the absence of a floating notification component, but as soon as the ToastNotification is ready, we should replace it.

Great news!
I've been seeing some sqlite incident reports of db corruption happening when inserting objects at a very high rate (e.g. https://sqlite.org/forum/forumpost/705955d7110e89a5)
In our case, during a blank installation of WikiLambda, there's an insertion of 1236 objects, with secondary db updates for each one of them. Running these inserts with sqlite & macOS seems to end up in a corrupted database quite often.