You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I maintain quickjs-ng1 (upstream of rquickjs) and I was wondering about the following:
Here you mention that openworkers-runtime-quickjs passes 16 of 17 tests.
Which tests are that? I assume they're not the tests in tests/ because they're not identical to e.g. openworkers-runtime-deno/tests.
Is it the tests generated with openworkers_core::generate_worker_tests!()? (Aside: I noticed that macro was removed from openworkers-core a few days ago. It's present in v0.5.1 though.)
Anyway, the reason I ask is that, if there's a spec compliance issue in quickjs, I can probably fix it, but I'll need to know what the exact issue is.
edit: is it the test_fetch_with_streaming_body test? It fails with:
Task should execute: Exception("Fetch handler failed: Exception generated by QuickJS")
1 I've also maintained rusty_v8 in the past. It's nice to see my projects being used in the wild. :-)
A bit of sleuthing revealed that globalThis.fetch tries to JSON.stringify the ReadableStream that is passed in options.body, and that fails with a "circular reference" exception because there is indeed a circular reference between the stream and its controller.
Not sure what the right fix is, but, on the positive side, at least it's not a quickjs bug.
Activity
bnoordhuis commentedon Jan 1, 2026
A bit of sleuthing revealed that
globalThis.fetchtries toJSON.stringifytheReadableStreamthat is passed inoptions.body, and that fails with a "circular reference" exception because there is indeed a circular reference between the stream and its controller.Not sure what the right fix is, but, on the positive side, at least it's not a quickjs bug.