Eduardo Pinto

Was discussing this with @franciscolopezsancho , @octonato and @aludwiko . We've agreed that this page will be useful to explain some concepts although we also agreed to break the dependency...

> Somehow related to this discussion, the runtime will retry in the case of a subscription failure, and a new span will be created. Is that what we want to...

Some weirdness going on here... failed as well for the previous kalix runtime version bump PR. Didn't look obvious at first sight.

another issue that could be prevented: https://github.com/lightbend/kalix-jvm-sdk/pull/2011

@aludwiko @octonato opened this side issue for discussion. I don't have a very good view on what this would entail effort-wise so feel free to expand on your thoughts. I...

We have this for ES entities now and I think we could consider it for Actions and Views. That is, you would be able to declare only a method for...

> An alternative would be to consider `String` to be the same as `Effect`. > > This will reduce quite a lot the boilerplate for cases where we want to...

We could even take this a step further possibly: - return (X != Effect) `effects().reply` - return CompletionStage `effects().asyncReply` - return DeferredCall `effects().forward` Now, if you want side effects, emitting...

Is this different from the component to component tracing?

So maybe [this one](https://github.com/lightbend/kalix-runtime/issues/2369) is fixed as well? I even wonder if it was a duplicate.