Vladimir Orany

why isn't this pull request merged, it looks terrific!

Indeed. I guess the most simplistic solution would be not to deduce additional environments once `test` environment is detected. At least the cloud ones.

thank you @dstepanov! is there something I can do for `@MicronautTest` test cases?

one can work this around by removing `scaffolding` plugin from the dependencies as the `fields` plugin is somehow linked to the issue

Thanks for fast response. Is this something which can be done directly in Micronaut libraries, ideally somewhere inside `AsyncInterceptor`? I believe this would be helpful for every Micronaut user.

Yes, the context is reused and you were right about the `shutdown`. I have created a test function and it looks like your suggestion with registering the futures works. So...

> Also, it would be nice to introduce a new event being triggered after the lambda function invocation, and this new scheduler can have a listener and do the awaiting...

I have started the work on the event here https://github.com/micronaut-projects/micronaut-aws/pull/1433

Just a few more details why we would like to keep `@Async` even in Lambda environment. We simply have a services which are shared between Micronaut applications and Micronaut functions...

Thanks for the link! It may be really handly!