Jonas Konrad

@dstepanov I don't believe other optimizations can work as well as this can. Even a very simple map takes some time for item access. Caching the last accessed annotation type...

On further testing in validation, I had to modify the API of this PR. ( https://github.com/micronaut-projects/micronaut-core/pull/11970/commits/da3c1f9ce89f5354632d4c7b3c91870bd3876134 ) It turns out that even the simple `.getMemoized` call can lead to an...

The warning is fixed in the latest snapshot. The timeout is not, however. It looks like the timeout happens on the server, so there's a time window where the client...

I can't reproduce it. But please stop using the `micronaut.netty.event-loops.*.executor` property, it can cause weird bugs.

what do you mean by "configure the event loops"?

That's fine. It's the `micronaut.netty.event-loops.*.executor` property specifically that you should not use. People incorrectly believe it solves some blocking operation issues, but it's snake oil.

The client uses netty. You can configure the event loop to run on a virtual thread, sure, but there's no point in doing so. Netty will just pin the carrier...

Yes, it is not a good idea to do blocking operations inside a suspended function. However I'm not sure what exactly is causing this particular behavior. It's possible that some...

So basically a deserialization variant of `@JsonRawValue`? Only works if the raw value is valid json of course, which is not required on the serialization side. I could see it,...

hmm that part of the test is supposed to match `micronaut.server.ssl.ciphers`, not sure why it's being ignored