Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plans for akka/pekko #4457

Open
jigarkhwar opened this issue Sep 1, 2023 · 4 comments
Open

Plans for akka/pekko #4457

jigarkhwar opened this issue Sep 1, 2023 · 4 comments

Comments

@jigarkhwar
Copy link
Contributor

Do you have any plans about moving to pekko or staying on akka?

@Isammoc
Copy link
Member

Isammoc commented Sep 1, 2023

See the same question (and answers) in Gatling community forum

@slandelle
Copy link
Member

CVE could be a reason to switch.

IMO, https://akka.io/security/akka-cve-2023-45865.html is very dumb, but might generate noise for us.
If so, we could consider switching.

(see apache/pekko#771 for the fix on the Pekko side)

@slandelle slandelle reopened this Dec 18, 2023
@slandelle slandelle added this to the 3.11.0 milestone Jan 9, 2024
@slandelle slandelle self-assigned this Feb 22, 2024
@slandelle slandelle modified the milestones: 3.10.5, 3.11.0 Mar 22, 2024
@slandelle slandelle removed this from the 3.11.0 milestone Apr 15, 2024
@slandelle slandelle reopened this Apr 15, 2024
@mveeprojects
Copy link

mveeprojects commented May 14, 2024

Hi @slandelle do you have an update on this? I see above that it was removed from the 3.11.0 milestone, do you have any information on when the move to Pekko might happen? Or what prevented it from being a part of the 3.11 milestone?

If it helps, I have raised a PR to contribute towards this effort.

@slandelle
Copy link
Member

Hi @mveeprojects
We're still considering several moves regarding Akka.
Please stay tuned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants