I have now experienced issues with JavaScript. A new function, Z23772, simply requires its input list of integers (from Natural numbers) to be returned (and converted to Integers). The JavaScript implementation fails with a list of seven ints (Z23777). With six ints, it passed in 743 ms (67 ms Evaluation), CPU usage 286.1.

An equivalent Python implementation succeeds with one int 6720 ms (5842 ms Evaluation), CPU usage 370.7. It fails with two ints 9798 ms (9014 ms Evaluation) CPU usage 577.5.

https://www.wikifunctions.org/view/en/Z23772

Z20086 is a good example for Rational numbers: failing if the list is not empty. I think we should consider this a Production Error.

May be related:
From Telegram

This is not what "Production Error" is for, so moving over to be a regular task.

In T391435#10748556, @Jdforrester-WMF wrote:

This is not what "Production Error" is for, so moving over to be a regular task.

Whatever… It may be P2 rather than P1, since it is limited to Python, but an inability to echo a list containing even a single item of some important types certainly feels like a production error. I did seek guidance when I raised the ticket but none was forthcoming.

In T391435#10751882, @GrounderUK wrote:

In T391435#10748556, @Jdforrester-WMF wrote:

This is not what "Production Error" is for, so moving over to be a regular task.

Whatever… It may be P2 rather than P1, since it is limited to Python, but an inability to echo a list containing even a single item of some important types certainly feels like a production error. I did seek guidance when I raised the ticket but none was forthcoming.

Who do you think would answer you in Telegram? The engineers generally aren't there, unlike Phabricator or the project chat. Seeing this task during the weekly triage was the first I ever heard of this. If you want us to see it sooner, as we have said before, please post it so we can respond rapidly.

Obviously I raised it here on April 9th. I don’t know how one is supposed to prioritise triage when raising a ticket but https://www.wikifunctions.org/wiki/Wikifunctions:Report_a_technical_problem#Discuss_with_others specifically refers to Telegram.

It seems like this problem may be associated with particular Types within Typed lists.

see https://www.wikifunctions.org/view/en/Z24212 where the test on natural languages works but a similar test on natural numbers doesn't.

Please could someone look at this as a matter of priority, just to determine whether it is a problem that only affects Production and whether it’s P1 or P2? Thanks!

The different underlying issues are being addressed in different phab tasks:
T393130: handle large log response: some fixes merged, but more to come
T392905: invalid result validation in one test causes indefinite "running" in all others: fixed and merged
T393152: Service utils logger fails with message containing stack trace: service-utils related issue, related fix is merged

Just noting that Typed pairs may have a similar issue in Python. We don't use them much, but https://www.wikifunctions.org/view/en/Z24645 works in Javascript (2163 ms), but fails in Python.

As far as I can tell, all the specific issues reported here have been resolved. Many thanks to everyone involved.

I am happy for this to be closed.

@gengh, could you please verify and close it?

In T391435#10760218, @99of9 wrote:

It seems like this problem may be associated with particular Types within Typed lists.

see https://www.wikifunctions.org/view/en/Z24212 where the test on natural languages works but a similar test on natural numbers doesn't.

This still seems to be a problem.

Thanks @99of9
It seems we need to continue investigating this issue.
Agreed: It appears to happen only on typed lists of particular types.

Observed only in the python implementation:

• Natural number: https://www.wikifunctions.org/view/en/Z24205
• Rational number: https://www.wikifunctions.org/view/en/Z24319
• Gregorian calendar month: https://www.wikifunctions.org/view/en/Z24320

Happening in all implementations (not sure if it's the same issue):

• Integer: https://www.wikifunctions.org/view/en/Z18622

Function: Discard tail of Typed list after first match/Z24203

Error 1: Typed List of Natural Number
/w/api.php?action=wikilambda_perform_test&format=json&wikilambda_perform_test_zfunction=Z24203&wikilambda_perform_test_zimplementations=Z24212&wikilambda_perform_test_ztesters=Z24205&uselang=en

• function: Z24203
• implementation: Z24212 (python)
• tester: Z24205

first function call returns error:

{
    "Z1K1": "Z5",
    "Z5K1": "Z500",
    "Z5K2": {
        "Z1K1": {
            "Z1K1": "Z7",
            "Z7K1": "Z885",
            "Z885K1": "Z500"
        },
        "Z500K1": "Could not serialize input Python object: 0"
    }
}

Error 2: Typed List of Rational number
/w/api.php?action=wikilambda_perform_test&format=json&wikilambda_perform_test_zfunction=Z24203&wikilambda_perform_test_zimplementations=Z24212&wikilambda_perform_test_ztesters=Z24319&uselang=en

• function: Z24203
• implementation: Z24212 (python)
• tester: Z24319

first function call returns error:

{
    "Z1K1": "Z5",
    "Z5K1": "Z500",
    "Z5K2": {
        "Z1K1": {
            "Z1K1": "Z7",
            "Z7K1": "Z885",
            "Z885K1": "Z500"
        },
        "Z500K1": "Could not serialize input Python object: Fraction(1, 2)"
    }
}

Error 3: Typed List of Gregorian calendar month
/w/api.php?action=wikilambda_perform_test&format=json&wikilambda_perform_test_zfunction=Z24203&wikilambda_perform_test_zimplementations=Z24212&wikilambda_perform_test_ztesters=Z24320&uselang=en

• function: Z24203
• implementation: Z24212 (python)
• tester: Z24320

first function call returns error:

{
    "Z1K1": "Z5",
    "Z5K1": "Z500",
    "Z5K2": {
        "Z1K1": {
            "Z1K1": "Z7",
            "Z7K1": "Z885",
            "Z885K1": "Z500"
        },
        "Z500K1": "Could not serialize input Python object: 1"
    }
}

Function: Concatenate two untyped lists/Z12767

Error 1: Join Typed lists of Integers (python)
/w/api.php?action=wikilambda_perform_test&format=json&wikilambda_perform_test_zfunction=Z12767&wikilambda_perform_test_zimplementations=Z12792&wikilambda_perform_test_ztesters=Z18622&uselang=en

function: Z12767
implementation: Z12792 (python)
test: Z18622

{
    "Z1K1": "Z5",
    "Z5K1": "Z507",
    "Z5K2": {
        "Z1K1": {
            "Z1K1": "Z7",
            "Z7K1": "Z885",
            "Z885K1": "Z507"
        },
        "Z507K1": "'ZObject' object can't be concatenated"
    }
}

Error 2: Join Typed lists of Integers (javascript)
/w/api.php?action=wikilambda_perform_test&format=json&wikilambda_perform_test_zfunction=Z12767&wikilambda_perform_test_zimplementations=Z18614&wikilambda_perform_test_ztesters=Z18622&uselang=en

function: Z12767
implementation: Z18614 (javascript)
test: Z18622

{
    "Z1K1": "Z5",
    "Z5K1": "Z500",
    "Z5K2": {
        "Z1K1": {
            "Z1K1": "Z7",
            "Z7K1": "Z885",
            "Z885K1": "Z500"
        },
        "Z500K1": "not a function"
    }
}

Error 3: Join Typed lists of Integers (composition)
/w/api.php?action=wikilambda_perform_test&format=json&wikilambda_perform_test_zfunction=Z12767&wikilambda_perform_test_zimplementations=Z13231&wikilambda_perform_test_ztesters=Z18622&uselang=en

function: Z12767
implementation: Z13231 (composition)
test: Z18622

{
    "Z1K1": "Z5",
    "Z5K1": "Z500",
    "Z5K2": {
        "Z1K1": {
            "Z1K1": "Z7",
            "Z7K1": "Z885",
            "Z885K1": "Z500"
        },
        "Z500K1": "not a function"
    }
}

Hello, all! There are two issues here. One is our current treatment of types in the orchestrator -> evaluator request, which should be fixed as of next deploy (currently blocked, unfortunately).

The other issue is that type conversion won't work when the list declares its type as Z1. To overcome this issue, list arguments can be wrapped in Z18475/Return typed list. This issue is discussed at length in this task.

I’m inclined to consider this problem beautifully resolved. Am I missing something?

In T391435#10888310, @cmassaro wrote:

Hello, all! There are two issues here. One is our current treatment of types in the orchestrator -> evaluator request, which should be fixed as of next deploy (currently blocked, unfortunately).

The other issue is that type conversion won't work when the list declares its type as Z1. To overcome this issue, list arguments can be wrapped in Z18475/Return typed list. This issue is discussed at length in this task.