Daniil Mikhaylov

Thanks for your answer, @wirthi Of corse I do what documentation say in second approach: 1) One Engine 2) Contexts are closed after invocation (through try-with-resource statement) 3) Every shared...

@wirthi The problem still presents on warming of graal context with caching

Checked this out on graal 19.3.0. The same. Also I forgot to attach heapdump initially. So where it is: https://drive.google.com/file/d/1pGQBM8pEFar1bXK7-3SIbOVXiCMCKgV-/view?usp=sharing

Hi @eleinadani I apologize this would like iterable chain of callbacks, that I can rebuild with API of Reactor (or something else) Also there is a case when callback return...

@pmlopes thanks for info. Looks like Promise resolving is not so easy if I need to follow https://promisesaplus.com/ Also polyfill is a good idea, but in our case we use...

@pmlopes Can you please share your polyfill or some part if possible?

@pmlopes Oh, I see. You just replace defualt with your own implementation. Thanks.

That looks will not work for me. because I want deffer evaluation to initial subscriber. In my casse I have reactive stream, that will emit value only on subscription. So...

@pmlopes Sorry for the inconvenience. I mean: ``` js: async function callFunction() { const a = await .. } ``` then in Java: ``` context.eval(promisePolyfillSource); context.eval(jsSource); // put callFunction to...

@pmlopes Yeah, looks working, but why I do not test it first, because it will be more complicated if I want to schedule my task on same scheduler and scheduler...