[00:34:22] Why do we need a built-in Z861? Since the built-in implementation didn't work on the first test, I made a composition just switching the arguments of the similar function we already have: Z26107 [00:43:38] Yes I thought we were all told to expect that large items wouldn't fetch yet. Isn't that still the status quo? (re @Al: Sorry, I thought everyone knew… please also see [[Talk:Z23753]]) [01:30:14] @dvd_ccc27919 what's the reason for disconnecting two of the implementations at Z17144? [03:27:29] Well, there's been significant progress over the last few months. Because of that, there are fewer timeouts involving Wikidata fetches. Also, once a large item has been fetched, it displays (after clicking on the wedge) much much more quickly than before. But yes, there's still more work to be done (and some underway). The reason I said "I didn't know about this" is [03:27:29] because I [03:27:29] wasn't aware of a failure pattern involving countries in particular. (re @u99of9: Yes I thought we were all told to expect that large items wouldn't fetch yet. Isn't that still the status quo?) [03:34:11] I don't think there is, they are just large items. [06:39:51] Because for some reason yesterday they didn't work (the "no implementation connected" problem). Now I've reconnected them (re @u99of9: @dvd_ccc27919 what's the reason for disconnecting two of the implementations at Z17144?) [07:43:32] …but I only got that working on Tuesday 😏 (re @u99of9: Why do we need a built-in Z861? Since the built-in implementation didn't work on the first test, I made a composition just swit...) [09:52:27] The built-in was rolled out after that, but yes it may have already been on course to arrive. Anyway unless there is good reason I think it's best to delete excess built-ins. (re @Al: …but I only got that working on Tuesday 😏) [10:36:26] Could be. I wonder whether we should explore the option of having built-in implementations for community functions rather than wrapping the built-in functions? I’m guessing that the code already existed in this case and was merely exposed as a built-in, but it is confusing to have parallel built-in and community functions. (re @u99of9: The built-in was rolled out after [10:36:26] that, bu [10:36:26] t yes it may have already been on course to arrive. Anyway unless there is good reason...)