-
Notifications
You must be signed in to change notification settings - Fork 18
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
refactor: Replace Akka with Pekko #2848
Conversation
71f76fa
to
00b220d
Compare
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2848 +/- ##
===========================================
+ Coverage 18.00% 88.04% +70.04%
===========================================
Files 281 243 -38
Lines 28899 23089 -5810
===========================================
+ Hits 5202 20329 +15127
+ Misses 23697 2760 -20937 ☔ View full report in Codecov by Sentry. |
Apache Pekko is a fork of Akka 2.6.x, prior to the Akka project’s adoption of the Business Source License. Version 1.0.0 is a direct replacement of Akka 2.6.x and has support for Scala 3 already. https://pekko.apache.org/
00b220d
to
018719e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See my comment in the RFC: I'm happy to see this merged.
All my remarks are details concerning imports. Feel free to ignore them.
Apache Pekko is a fork of Akka 2.6.x, prior to the Akka project’s adoption of the Business Source License. Version 1.0.0 is a direct replacement of Akka 2.6.x and has support for Scala 3 already. https://pekko.apache.org/
See also the RFC for the proposed switch: https://www.notion.so/review-RFC-006-Replace-Akka-with-Pekko-12c2199a8bff43adb4d907073d33e878?pvs=4
Pull Request Checklist
Task Description/Number
Issue Number: DEV-2709
Basic Requirements
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
Does this PR change client-test-data?