Valery Silaev
Valery Silaev
Challenge accepted )
Hello, The issue is acknowledge, but the fix is pending to the _second_ release. The reason behinds the behavior observed is that internally async/generator methods are transformed into anonymous internal...
Unfortunately, this task is get out of my radar ( Regardless of my brave release numbering, the project still has issues with scheduler resolvers (already addressed, to be released shortly),...
Hi! TBD is for docs only, the functionality itself is implemented. 1. You always can use `Future.cancel(true)` on the `CompletableFuture` / `Promise` / `CompletionStage` (with the upcast to the `Future`)...
Selector.select() should be interrupted in this case, no? Can you create a minimal test app that demonstrates the issue?
I need some real code to comment. Try to do the most straightforward thing: 1. use annotated with @SchedulerProvider async method parameter of type Scheduler 2. for Scheduler use interruptible...
Closing issue as far as no follow-up from the issue opener
Non-continuable method calling continuable method leads to OOM instead of not instrumented exception
Is stack trace that short or is it truncated by you? Typically, in such scenario `StackOverflowException` occurs earlier than `OutOfMemoryException`...
Non-continuable method calling continuable method leads to OOM instead of not instrumented exception
Verified. Indeed, the code with non-continuable method calling continuable method creates an infinite loop here. You can check it if N=10 (any small number). Raising the number of iterations just...
Created a [PR](https://github.com/beehive-lab/TornadoVM/pull/61) that overcome the limitation (inability to set VM-wide default driver/device).