User Details
- User Since
- Jul 7 2020, 8:30 PM (211 w, 1 d)
- Availability
- Available
- LDAP User
- DVrandecic
- MediaWiki User
- DVrandecic (WMF) [ Global Accounts ]
Yesterday
The function explorer in fact allows you to check on other functions too, out of the widget. It is indeed meant as a widget to explore functions. If there are no more feedback on this, I would close this as invalid.
Tue, Jul 16
For now, we don't support type conversion on untyped lists, or on functions that return a Z1. That's indeed a missing feature still.
I also cannot replicate it as of today, tried several ways. Maybe has been serendipitously fixed. Shall we close it?
Mon, Jul 15
The issue was also present on Z16053 and Z17506.
For some reason, two edits in quick succession added Z13911 twice to the Z8K4 on Z13909:
Fri, Jul 12
Geno is asking what to put in the summary and suggests the orchestration time directly. That sounds right!
For JavaScript, the type annotation proposal seems stuck: https://tc39.es/proposal-type-annotations/
Wed, Jul 10
+1 to Amin
Tue, Jul 9
Besides size, @gengh also mentioned some escaping that might be going astray.
Fri, Jul 5
If easy. yes, change that as well in this task. If not, feel free to make a new ticket for that.
Sat, Jun 29
There were two bugs in the involved objects, which I fixed:
Thu, Jun 27
Background reading: https://www.wikidata.org/wiki/Wikidata:Data_access
Wed, Jun 26
Here's what I did:
- I created a Function that takes a string and returns a Type
- I created an Implementation for that function that is a composition and does Z801(Z6)
- I created another Function that takes a Type and returns a String
- I created a test that runs this new function on the function created in step 1 and expects a Z6K1 (see screenshot 1)
- I created an implementation for that function that is a composition and does Z803(Z3K3, Z811(Z803(Z4K2, K1))) (i.e. take the key id of the first of the list of keys of the given argument) (see screenshot 2)
- The test passes
That's correct, both *should* be the same. The issue is that if a timeout occurs, as is here the case, unfortunatley, it may depend on the exact timing of the timeout which errors get exactly reported. Did the time run out during evaluation, orchestration, execution, validation, parsing, rendering? In each of these cases we might have slightly different error messages.
Oh, weird. Indeed, can confirm, I cannot see it on the implementation Z11223 anymore.
I found a simpler place where the same behavior can be observed:
https://www.wikifunctions.org/view/en/Z10174
This might be the same as T360331
Jun 24 2024
Jun 18 2024
Jun 12 2024
I am closing this one since Z844 is now the Z4K4 on Z40 anyway, it was jut that I had an old database.
Jun 11 2024
Jun 5 2024
Jun 4 2024
I just realized two things:
- I am using Vince's sqlite db because the original upload of the data doesn't work
- That doesn't have a Z4K4 key defined on Z4!
Jun 3 2024
May 23 2024
Let's timebox the investigation and fix for now in order to figure out what is going on. Say two days, and then write down the status. We should figure out why seemingly slower implementations are ranked higher. Another example where this happens is on Z16137: https://www.wikifunctions.org/wiki/Z16137
May 22 2024
Once this is done, we can also close T343748
May 16 2024
May 13 2024
May 11 2024
Thanks for filing the more specific bug about getting the Z1K1 value.