Can't use alpha version: TypeError: WebAssembly.Function.type is not a function about pyodide HOT 4 CLOSED

Thanks for the report @kor0p!
Indeed they seem to have changed this from Chrome 119 to Chrome 120. Of course, it only reproduces if you turn on Experimental WebAssembly JavaScript Promise Integration (JSPI) in chrome://flags. I'd want to keep JSPI support for node v20 so we'll have to feature detect this and choose the appropriate way to get the type of a wasm function.

from pyodide.

Thanks for the test @kor0p. If you make a PR adding that to the test suite I'll merge it.

from pyodide.

@hoodmane
Thanks for quick answer
Yes, I have enabled this flag to test JSPI, so I disabled it (and reopened browser) and still can reproduce the bug here 😢

Bug is gone only when I disable flag "Experimental WebAssembly"

from pyodide.

@hoodmane Thanks a lot!
Now I can try JSPI feature as expected!
So, I went to original PR to find some examples on it (tests should be great examples, isn't it?)
And there is no tests for explicit Python PyodideFuture usage. But it works the same way, and it's great news, that we finally can syncify() it!
Here is draft for such test:

@pytest.mark.xfail_browsers(safari="No JSPI on Safari", firefox="No JSPI on firefox")
def test_syncify_create_task(selenium):
    selenium.run_js(
        """
        await pyodide.runPythonSyncifying(`
            import asyncio

            async def test():
                await asyncio.sleep(0.1)
                return 7

            task = asyncio.create_task(test())
            assert task.syncify() == 7
            del test, task
        `);
        """
    )

from pyodide.