just_ppe

Pasting answer from Discord here as well, for transparency ;-) Two things here: 1. it's weird that you can't download the data from the Warp GW itself - this indeed...

> Perhaps we need executePendingJobs after resolvePromise? I've missed your answer. Unfortunatelly this didn't help.. :-( I've also tried sth stupid like: ``` const code = ` async function handle(state,...

@tzarebczan , would like to have this feature directly in the SDK, or in the DRE nodes?

@arcj0 , can you please try with `1.4.42` ?

One more experiment: ``` const mem1 = new WebAssembly.Memory({ initial: 256, //*65536 maximum: 256 //*65536 }); const variant1 = newVariant(RELEASE_SYNC, { wasmMemory: mem1 }); const QuickJS1 = await newQuickJSWASMModule(variant1); const...

> If I understand correctly, I think this would be expected because these two objects are the same object. I think it works similar to this: > > ```js >...

> You can get the memory address of various objects like QuickJSContext, QuickJSRuntime by inspecting their private internals looking for pointer types. You’ll need to use the private constructor to...

ok, here's what I've got so far ``` // module 1 const mem1 = new WebAssembly.Memory({ initial: 256, //*65536 maximum: 256 //*65536 }); const variant1 = newVariant(RELEASE_SYNC, { wasmMemory: mem1...

Another try - by passing pointer to the context in the `ContextOptions` ``` // module 1 const mem1 = new WebAssembly.Memory({ initial: 256, //*65536 maximum: 256 //*65536 }); const variant1...

One last try - with creating both runtime and context from pointers: ``` // module 1 const mem1 = new WebAssembly.Memory({ initial: 256, //*65536 maximum: 256 //*65536 }); const variant1...