Johan Andrén

BTW I think this is a mix of the two tests `EventSourcedBehaviorLoggingInternalLoggerSpec` and `EventSourcedBehaviorLoggingContextLoggerSpec` failing pretty consistently on JDK 17, Scala 3. `EventSourcedBehaviorLoggingSpec` being a common supertype.

I've seen this many times as well. And recently, just after such a loop, not sure if it is related at all: ``` [error] akka-serverless/akkaserverless-java-sdk/sdk/java-sdk/src/main/scala/com/akkaserverless/javasdk/impl/replicatedentity/InternalReplicatedData.scala:20:27: object replicatedentity is not a...

Generated docker file says `ENTRYPOINT ["/opt/docker/bin/customer-registry"]` but staged image contents contain `bin/main` rather. Where does that expected entry point name come from?

Let's hold this off if bumping to 3.9 is enough for now.

Needs to be checked with the R2DBC plugin support first.

They do document it, but only for the spring/code first SDK, not for the protobuf ones: https://docs.kalix.io/java/actions.html#_forwarding_headers

Needs a scalacheck bump as well

I think I did a change in #3350 for same mima failure (more git history in the checkout)

Spent some time on trying to read the sbt `logLevel`, but that is not set by default, also tried to coerce it out of the sbt logger but didn't manage....

Looking at the specs the two versions are identical except some comments, the package and some language specific options for java and go, so will be easy to implement both...