This room is dedicated to discussions between Akka committers for coordinating the development process—for general questions and discussions around the usage of Akka please head over to akka/akka. For more info see: http://bit.ly/akka-gitter
I'm preparing a small workshop at work about Akka, and I was re-reading the docs and I found that "how to deal with blocking APIs in Actors" is pretty hidden. Currently I could only find this information under https://doc.akka.io/docs/akka/current/typed/dispatchers.html#blocking-needs-careful-management Do you think it should be more prominent?
shall I open a ticket to discuss it?
a PR will follow, but I wanted to have first a ticket so people could give their opinion if anybody has a strong one
creating an actor with
system.actorOf(Props[StashTest]) as in the docs produces a warning on scala 2.13 (it wants the parens, system.actorOf(Props[StashTest]())). Unfortunately removing the parens from the Props apply method would be source-incompatible, so I guess we want to move to using system.actorOf(Props[StashTest]()) in docs, right?
One question about docs, on Akka Classic there was this nice diagram: https://doc.akka.io/docs/akka/current/actors.html#actor-lifecycle but for Akka Typed there isn't any. Is this intentional?
Can someone help me understand why is there a
Try here? https://github.com/akka/akka/blob/v2.6.9/akka-actor/src/main/scala/akka/pattern/BackoffSupervisor.scala#L318 Under what conditions could this throw?
And the issue: akka/akka#24419
I'm having a look at the neat new features around cluster aware shard allocation and rolling updates (akka/akka#29548). I'm wondering if those would play well in case of rollback to an older version, was that discussed already, are there recommendations about that?
So that means a rollback will be suboptimal. Could perhaps be worked around by assigning a higher version number to the previous version and rollback by deploying that.
I think rollbacks should be the exception though, so perhaps ok if that is suboptimal as long as it still works.
I either found a bug on the docs or the code for Akka Typed supervision: https://github.com/jlprat/Akka-Lunch-and-Learn-Sessions/blob/master/src/test/scala/io.github.jlprat.akka.lnl/supervision/InitializationTest.scala#L58 fails given this Behavior: https://github.com/jlprat/Akka-Lunch-and-Learn-Sessions/blob/master/src/main/scala/io.github.jlprat.akka.lnl/supervision/typed/Initialization.scala#L62
And according to https://doc.akka.io/docs/akka/current/typed/fault-tolerance.html#child-actors-are-stopped-when-parent-is-restarting I'd say that the
And according to https://doc.akka.io/docs/akka/current/typed/fault-tolerance.html#child-actors-are-stopped-when-parent-is-restarting I'd say that the
setup block should be re-executed on restart. Am I doing something wrong? or did I stumble upon a bug?
We'll release Alpakka Kafka 2.1.0-M1 with the Kafka 2.6.0 client and required Akka 2.6 tomorrow akka/alpakka-kafka#1238
Can anyone guide me how to remove this error
@aggarawalrishav_twitter this is the gitter channel for us developing Akka itself, for questions about using Akka, please use the akka/akka channel or the forums over at https://discuss.akka.io
I want to know how to compile akka-2.6.8?
I get some problems like: [error] Nonzero exit value: 128
Hi @WTFGEDelphia have you tried this? https://github.com/akka/akka/blob/master/CONTRIBUTING.md#getting-started-with-sbt