Kevin Wooten

Yep it was the clean that was needed. For posterity here is my reproducer that generates the same error. [code-with-quarkus.zip](https://github.com/quarkusio/quarkus/files/9734918/code-with-quarkus.zip)

Adding the `quarkus-resteasy-reactive-kotlin` explicitly appears to solve the issue.

@glefloch Anything I can do to speed this up? Holding up our update.

A reproducer that passes with `2.12.1.Final` and fails with `EndpointIndexer` with `2.13.1.Final` [code-with-quarkus.zip](https://github.com/quarkusio/quarkus/files/9821260/code-with-quarkus.zip)

As an implementor of a fully compliant JDBC driver for PostgreSQL (http://github.com/impossibl/pgjdbc-ng)... please let me suggest allowing local times here is the wrong path. JDBC did this in its first...

@vietj https://github.com/impossibl/pgjdbc-ng is a JDBC 4.2 compliant driver built on an asynchronous Netty core; I am the author. One of the central tenants of the driver is to use a...

FYI, the reason I bring this to your attention is that you specifically talked about mapping OIDs to codecs and that's what pgjbdc-ng does.

Scratch that... we _*could*_ redirect all logging if we set this variable in every single procedure we define but that is cumbersome and error prone.

Also, all the documentation about custom logging appears woefully out of date with the latest. Currently we are setting the `Log.writer` variable directly; maybe part of the issue is we're...

Not being able to redirect your `system` means we lose the ability to trace problems related to procedures after the fact using our online logging platform. The messages are ___extremely___...