Jonas Konrad comments

Results 268 comments of


                                            Jonas Konrad

Only One Subscriber Allowed Error After Migrating to Micronaut 4.2.x

Potentially it will happen but there's no timeline.

NPE "io.micronaut.http.filter.FilterContext.response()" because "newFilterContext" is null

I tried many times and also in an infinite loop with curl, wasn't able to reproduce the issue

NPE "io.micronaut.http.filter.FilterContext.response()" because "newFilterContext" is null

Interesting, maybe there's something wrong with CSRFFilter

Add support for Guava `ImmutableIntArray` / `ImmutableDoubleArray`

LGTM, but have you already signed the CLA?

missing gradle examples

Maybe you can take a look at the micronaut integration. For micronaut, we decided to use only minimal code in the OSS-Fuzz repo, and implement the rest in a gradle...

Annotated with @ClientFilter filters are not used during bootstrap calls ?

@graemerocher I think this broke on the consul side. Annotation driven filters have never worked in the bootstrap context because method processors are not called there, we've run into this...

Annotated with @ClientFilter filters are not used during bootstrap calls ?

still something we should fix long term in core.

DefaultAccessorNamingStrategy converts to lowercases the whole first group of uppercase characters

The reason is abbreviations, e.g. HTMLParser -> htmlParser. That this doesn't work well with lombok is a known issue.

DefaultAccessorNamingStrategy converts to lowercases the whole first group of uppercase characters

Maybe USE_STD_BEAN_NAMING is enough to fix your particular case.

Changes to the request URI through Micronaut's HTTP @Filter are ignored.

No, it's in the backlog.