Johan Andrén

Can't safely bump before we know the underlying R2DBC connector supports 2.3.232

https://github.com/akka/akka-persistence-r2dbc/actions/runs/12960908352/job/36155423021#step:6:1186

https://github.com/akka/akka-persistence-r2dbc/actions/runs/18875391860/job/53863731543#step:9:319

42.7.2 is what the R2DBC driver is tested against but we are already one patch ahead so maybe this is fine given that all tests still pass?

Not entirely sure we want to go out of line with the underlying r2dbc driver. @patriknw any opinion?

r2dbc-postgresql 1.0.7.RELEASE bumped but that is still on 42.7.2

Sorry for very late response. I agree, that seems somewhat surprising. An even easier reproducer would be: ``` val log = LoggerFactory.getLogger(classOf[QuickstartApp.type]) val futureBinding = Http().newServerAt("localhost", 8080).bindFlow(Flow[HttpRequest].mapAsync(1) { req =>...

Can you share an example server route that reproduces this?

Thanks, surprising indeed that the options directive does not "consume", I'd say that is the issue, was expecting something like a lower level request handler not discarding the request entity...

Needs to be checked with the R2DBC plugin support first.