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
Hi hAkkers!
I just have a quick question: what is the status of JDK17? Is it safe to use with Akka right now? I think I have seen at least one open ticket about it, but I wanted to ask here. I think some of the naughty tricks here and there internally might no longer work? I rather ask you before learning the issues in runtime :D
I just have a quick question: what is the status of JDK17? Is it safe to use with Akka right now? I think I have seen at least one open ticket about it, but I wanted to ask here. I think some of the naughty tricks here and there internally might no longer work? I rather ask you before learning the issues in runtime :D
1 reply
we do still use some naughty tricks, but I think they all fall in the category that (by default) JDK17 still only warns about
not 'officially officially' AFAIK, but I'm fairly sure we'd want to prioritize any issues in that area ;)
@ennru Regarding https://github.com/lightbend/sbt-paradox-project-info/pull/18#issuecomment-1063768315 I am going to send through a set of PR's that will update various things for sbt-paradox-project-info in addition to the github-actions/CI (such as updating scalafmt etc etc)
It will be similar to tbe PR's I have done here https://github.com/johanandren/futiles/pulls?q=is%3Apr+author%3Amdedetrich
eg:
flatMapPrefix which passes in an java.lang.Iterable but groupedWithin gives a java.util.List
I think the value akka passes out should be more specific type and the value user return to akka should be more generic.
1 reply
So I went ahead and removed the hardcoded lightbend readiness levels from sbt-paradox-project-info and made them configurable along with a sample sbt-plugin for specific use with Lightbend/Akka projects, see lightbend/sbt-paradox-project-info#34 for more info
https://www.techempower.com/benchmarks/#section=data-r20&hw=cl&test=fortune Should do another round to tune akka-http?
2 replies
intreasting to see akka benchmark in kt coroutine project
(I do contribute also when time permits :joy: )
https://github.com/LesnyRumcajs/grpc_bench/wiki/2022-04-23-bench-results new benchmark result is out
https://github.com/LesnyRumcajs/grpc_bench/pull/227/files
https://github.com/LesnyRumcajs/grpc_bench/pull/232/files
Have no idea is these two related
https://github.com/LesnyRumcajs/grpc_bench/pull/232/files
Have no idea is these two related
I think it's ok to add an overloaded
collect method to Sink Flow which accepts a factory of collector.
And as the
Collector always return a new container maybe the factory is not needed ,but just a collector.
Hi everyone !
I'm a PhD student and I'm currently working on writing a transactional shared memory with causal consistency guarantees for actors.
I have a working prototype that I wish to test. Has any one ever tried to run Jepsen's test suite with Elle on Akka?
Thanks !
I'm a PhD student and I'm currently working on writing a transactional shared memory with causal consistency guarantees for actors.
I have a working prototype that I wish to test. Has any one ever tried to run Jepsen's test suite with Elle on Akka?
Thanks !
2 replies
So I think I have found a memory leak in Alpakka's S3 client, reported an issue at akka/alpakka#2866. Still looking into it, will report any progress on the issue
I think Kalix needs some section about gradle not just maven
1 reply
So I have just made an in progress PR for adding
SinkWithContext to akka-streams, most of it is done however I came across a blocker which is I described here https://discuss.lightbend.com/t/concat-partition-doesnt-appear-to-work-when-combining-sinks/9822
2 replies
PR opened for Alpakka which implements the new
S3.getObject that has a far more idiomatic API and no longer contains a possible memory leak akka/alpakka#2874
