Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Oct 26 07:39
    patriknw labeled #29767
  • Oct 26 07:39
    patriknw labeled #29767
  • Oct 26 07:39
    patriknw labeled #29767
  • Oct 26 07:39
    patriknw labeled #29767
  • Oct 26 07:38
    patriknw commented #29767
  • Oct 26 07:07
    patriknw commented #29765
  • Oct 26 06:56
    patriknw commented #25468
  • Oct 25 16:21
    nitikagarw commented #25468
  • Oct 24 21:20
    akka-ci commented #29672
  • Oct 24 21:05
    dope9967 commented #29672
  • Oct 24 21:03
    akka-ci commented #29672
  • Oct 24 21:03
    akka-ci unlabeled #29672
  • Oct 24 21:03
    akka-ci labeled #29672
  • Oct 24 20:44
    dope9967 synchronize #29672
  • Oct 24 20:31
    akka-ci unlabeled #29672
  • Oct 24 20:31
    akka-ci labeled #29672
  • Oct 24 20:26
    dope9967 synchronize #29672
  • Oct 23 16:16
    ennru demilestoned #24444
  • Oct 23 16:16
    ennru reopened #24444
  • Oct 23 16:16
    ennru commented #24444
Corey O'Connor
@coreyoconnor
I haven't been involved with a new release yet :) so not sure
Enno
@ennru
The setup seems quite manual https://github.com/akka/akka-persistence-dynamodb/blob/master/RELEASING.md and requires access to the Akka Sonatype account.
It might be good to improve the process.
Corey O'Connor
@coreyoconnor
Previously I was told to message this group to request a release. That was quiet a while ago so I would imagine there are some improvements possible.
looks like I have a few changes to make before release tho
Enno
@ennru
Yes, someone from the core Akka team will have to run the release so it gets published to Sonatype. Please prepare as much as possible.
davidlzs
@davidlzs
Should the documentation on https://doc.akka.io/docs/akka/current/stream/stream-composition.html be updated to use Flow.fromSinkAndSourceCoupledMat or Flow.fromSinkAndSourceCoupled rather than the deprecated CoupledTerminationFlow.fromSinkAndSource?
Enno
@ennru
Yes, that would be great to get updated.
Arnout Engelen
@raboof
hmm, will NegotiateNewSession still be relevant after Akka 2.6? I see TLSActor can still receive it, but I don't see where it would be sent. Aside that it seems it's only used in deprecated methods.
davidlzs
@davidlzs
@ennru Pull request akka/akka#29381 created.
kerr
@hepin1989
https://github.com/openjdk/loom Seem like they do accept contributions from the community too, will Akka contribute some for future design?
Patrik Nordwall
@patriknw
New Akka team plan akka/akka-meta#138
Josep Prat
@jlprat
After a looooong break, I did send another PR for Akka :D it's just a typo though...
Josep Prat
@jlprat
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?
Enno
@ennru
@jlprat Great to see you around. Yes, we might need more pointers to it. If you identify good spots where it seems to make sense to link there, you may just open i PR.
Josep Prat
@jlprat
@ennru took me too long, but here there is a ticket: akka/akka#29544
a PR will follow, but I wanted to have first a ticket so people could give their opinion if anybody has a strong one
Arnout Engelen
@raboof
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?
Johan Andrén
@johanandren
I agree
Enno
@ennru
We'll cut an Alpakka Kafka release in the next days akka/alpakka-kafka#1191
Josep Prat
@jlprat
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?
Patrik Nordwall
@patriknw
Maybe some of that is still relevant for Typed, but many things are not, such as ActorSelection. Actor path is less relevant since receptionist is used instead.
Patrik Nordwall
@patriknw
New Akka team plan akka/akka-meta#140
Enno
@ennru
We plan to cut Alpakka 2.0.2 tomorrow akka/alpakka#2407
Kris Kalavantavanich
@kkalavantavanich
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?
Johan Andrén
@johanandren
This is the commit it was added, so duration overflow perhaps? akka/akka@7ba40b2
And the issue: akka/akka#24419
Kris Kalavantavanich
@kkalavantavanich
Ah, I see. Thanks.
Arnaud Burlet
@fredfp
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?
Johan Andrén
@johanandren
It will prefer the higher version when there are multiple, but will avoid rebalance when there are more than one version.
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.
Arnaud Burlet
@fredfp
I agree that rollbacks should be the exception, but when those happen it's most likely a bad situation already. What I fear is that all shards end up allocated on the last surviving node with the newer version, before finally moving to older versions once that last node exits
Johan Andrén
@johanandren
Only if the shards are allocated during rollback, that only happens if they get a request exactly then or you are using remember entities.
Johan Andrén
@johanandren
Created an issue to discuss/track this: akka/akka#29667
Arnout Engelen
@raboof
I'm getting ready to release Akka HTTP 10.2.1
Enno
@ennru
We've started to work on things for Alpakka Kafka 2.1.0 akka/alpakka-kafka#1211 -- please chime in.
Arnout Engelen
@raboof
seeing a lot of IOException: Error accessing /home/travis/.ivy2/cache/com.typesafe.akka/akka-actor_2.13/jars/akka-actor_2.13-2.5.27.jar on travis - throwing away the cache.
Josep Prat
@jlprat
I suspect that is due to the use of Synchronous testkit instead of the asynchronous. If this would be the case, I would argue this is a bug (or missing functionality) with the synchronous testkit.
Josep Prat
@jlprat
so, apparently the Synchronous testkit doesn't really work nice with supervision, is this a known limitation?
Josep Prat
@jlprat
I created an issue for this :point_up: akka/akka#29767
Enno
@ennru
Thank you @jlprat -- sorry for the radio silence here
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
Josep Prat
@jlprat
Understandable @ennru I would need to look deep into the testkit code to see if it's a missing feature or just a bug
Enno
@ennru
Alpakka is ready for changes going into the next major version! akka/alpakka#2455
pruthvi578
@pruthvi578
How to materialize 1 Flow and use it over-and-over with different http get requests. Please provide some examples
r9636
@r9636
How can I consume messages from kafka in AKKA FSM in java?
Patrik Nordwall
@patriknw
Pls use akka/akka channel for questions of how to use Akka. This is for developing Akka itself.
r9636
@r9636
Yep thanks