Renato Cavalcanti

Oh gosh! The error is consistent and it happens each time on this PR: https://github.com/akka/akka-projection/pull/639 And the PR is updating Testcontainers. Need to see if it's worth updating the image...

No, I saw it on a PR build. I didn't link here because the link gets invalidate when we retriggered it.

@hseeberger, I wonder if you stripped the quotes when create the schema manually. The method `SlickProjection.createOffsetTableIfNotExists(databaseConfig)` is creating the schema defined in https://github.com/akka/akka-projection/blob/6b1668c368a7d6a034391d65bed8d7f1fee24cb1/akka-projection-jdbc/src/main/scala/akka/projection/jdbc/internal/Dialect.scala#L42-L58 And we have a test that checks...

For reference: https://github.com/slick/slick/issues/2064

@hseeberger, on the other hand, I think it's odd to be bound to an issue in Slick. I have looked further and we can remove these restrictions if we let...

We may improve how we deal with quotes table names and columns on a future release. I'm removing this from milestone 1.0.0, but keeping it open.

> One concern about adding ProjectionDaemon is that then we need the akka-cluster-sharding-typed dependency just for this. But this is an important dependency since that's The Recommended way of running...

I think the `ProcessProvider` won't help much. We still have to deal with the protocol message. And if we introduce a `DaemonBehavior`? The ShardedDaemon should work with any `Behavior`, but...

So, if we don't have to deal with the protocol when using `ProcessProvider` it means that somewhere we will have a `DaemonBehavior` that we will initialize behind the scenes with...

I think you are right for the `compareAndSet`. It's true that if it's failing for an intermittent reason, you better wait or solve the source of the failure. I would...