pekko icon indicating copy to clipboard operation
pekko copied to clipboard

Build highly concurrent, distributed, and resilient message-driven applications using Java/Scala

Results 100 pekko issues
Sort by recently updated
recently updated
newest added

relates to https://github.com/apache/pekko/pull/1324 See failures in JDK11 builds in https://github.com/apache/pekko/actions/runs/9104380012/job/25028122890 The affected sbt calls only happen when Java version is 11 due to conditions in the workflow yml.

I'm reopening here an [issue that I reported at the time under the akka repo](https://github.com/akka/akka/issues/31095). We had a case where an issue on a single node lead to the whole...

bug
help wanted
needs-reproducible-test

Both EventSourcedBehavior and Durable state seem to be exposed to stack overflow exceptions when lots of read-only commands are in the stash. This bug has already been opened as an...

bug
help wanted
needs-reproducible-test

Found something we could optimized it. ------- DO NOT MERGE until I have added some tests for it.

Make code cleaner, it is basically the same. ## Before using https://github.com/apache/pekko/blob/b5eb6ff01a8d5c5f50b5d1b54280c0dcb075a59a/actor-typed/src/main/scala/org/apache/pekko/actor/typed/scaladsl/adapter/PropsAdapter.scala#L31-L36 ## After https://github.com/apache/pekko/blob/b5eb6ff01a8d5c5f50b5d1b54280c0dcb075a59a/actor-typed/src/main/scala/org/apache/pekko/actor/typed/internal/adapter/ActorSystemAdapter.scala#L125-L133

Motivation: Add virtual thread support Modification: Add a virtual thread executor Result: Virtual thread support was added. TODO: I think it would be nice to add the blocking io dispatcher...

Unfortunately, docker-java has a lot of outdated dependencies - many with CVEs. https://mvnrepository.com/artifact/com.github.docker-java/docker-java/3.3.6 If and when we uptake a new docker-java, we can review if we still need some or...

I was following the online tutorial on the official `Pekko` website: https://pekko.apache.org/docs/pekko/current/typed/guide/tutorial_4.html#:~:text=Keeping%20track%20of,%C2%B6 and I found that `DeviceTerminated.groupId` may not match with `DeviceGroup.groupId` but we don't handle such a case right...

In pekko 1.1, we are encouraging libs to have a failed future if `deleteObject(persistenceId, revision)` doesn't delete rows. https://github.com/apache/pekko/pull/1271

The link validator is currently run on PR validation, however it is far too susceptible for intermittent failures not caused by the PR in question. We should probably move it...