* Not working for mysterious reasons
* Fix for #27507 race in test
Logging at debug to try if there is a race when testing on Jenkins
Also, fail fast if expecting a signal from a TestProbe (never happens)
Some minor logging improvements for event sourced behavior as well.
* Don't send batches of events when snapshot and event deletion is enabled
When events are deleted the event sourced actor switches to running until it gets
an ack back from the journal about deleting events, then it deletes snapshots if that
is enabled. This means events and snapshotting could happen inbetween making the
ordering of SnapshotComplete and DeleteSnapshotsComplete signals non deterministic.
* Config to exclude class prefix from serialize-messages, #24273
* Adding no-serialization-verification-needed-class-prefix, with "akka." included
by default
* This is important now when we disable Java serialization by default.
There will be many complaints about Akka internal classes that are not marked with
NoSerializationVerificationNeeded, and we can't really sprinkle that everywhere.
* Not removing NoSerializationVerificationNeeded usage in Akka classes because that
may break bin compat, even though it's needed any more.
* fix DisabledJavaSerializerWarningSpec
* Eager creation of system materializer on system startup #26850
* System level materializers always spawned under a specific system actor #26850
* No need for RepointableActorRef logic anymore
* MiMa filter
* Make the creation timeout higher
* LogCapturing for ClassicSupervisingTypedSpec
* LogCapturing for AdapterSpec
* Spelling in AdapterSpec
* LogCapturing for JoinConfigIncompatibilitySpec and JoinConfigCompatibilitySpec
Also: updates to test to actually verify what they say they verify
* Review feedback fixes
* No depend on AkkaSpec.config
Move utils to construct PersistenceId
* Move from EntityTypeKey to PersistenceId
* Thereby no persistence dependencies in sharding
* Reference documentation PersistenceId and how to use with Sharding
* Add EntityTypeKey to EntityContext to make it "complete"
* One consequence of adding EntityTypeKey to EntityContext is that
now requires additional message type parameter and then type inference
for `init` (Entity) breaks down. Solved by using two parameter lists in
Entity.apply, which is pretty nice anyway since the second parameter is
a function.
* as bonus the dependency can be removed
* Use akka.japi.function types for adapter lambdas
The Java lambda types does not allow for throwing exceptions but
because of how we run the adapter lambdas in-actor that is fine, so
use our own akka.japi.function types to allow for that.
* Use akka.japi.function types for lambdas where it makes sense
