This should have been implicit with the -release flag, and now
this indeed appears to be the case. Tested with 2.12 and 2.13.0
Fixes the scalac part of #27079
* Problem could be recreated with DowningProviderSpec when running
with -Dakka.remote.artery.enabled=off
* The exception from the downing provider caused cluster shutdown
followed by CoordinatedShutdown and ActorSystem.finalTerminate
* The ActorSystem had still not fully initialized so it tried to
load the configured extensions and the SystemMaterializer extension
* SystemMaterializer can't create child actor
* The thrown exception isn't wrong but might be confusing
* Skip loading extensions if ActorSystem already terminated
* The reason for different behavior with Artery and classic remoting
is that Artery inits the SystemMaterializer earlier
* sometimes failed: "WriteAggregator with delta must timeout when less than required acks"
* the DeltaNack will trigger immedediate send of Write
* seems to be a race condition of when the probe is receiving the Write
from the DeltaNack vs the last expected DeltaPropagation
* Use embedded media driver for StressSpec
The current setup starts a media driver for each JVM in the same
directory which is caused the cnc file to be courruped in some way
so that the client in Akka timed out waiting for it to be initialized.
This test is disabled for Artery, see
https://github.com/akka/akka/issues/21810 so all it does is startup
and then end the test right away.
Will look at enabling the test again separately.
Fixes#27030
Only akka-actor got the protobuf files due to the assembled jar being
added to the unmanaged jars for ease of use when importing into
Intellij. Removing that from default settings seems to have fixed it.
Fixes
* Remove protobuf Any import from doc spec
* scaladsl.PropsAdapter and javadsl.Adapter.props should use stop supervision,
otherwise it will restart (from classic) by default
* PropsAdapter is used by Cluster Singleton and Sharding
* also typed.ActorSystem.systemActorOf
* removed default param value in internal.PropsAdapter to make the
decision of rethrowTypedFailure more explicit
* rethrowTypedFailure=true is used for the child faild propagation to
parent and only makes sense when the parent is Typed
* stream: debug dot output should point `shouldPush` in the right direction
* stream: also support Pushing and Pulling states for ConnectionSnapshot
Using ShouldPull for Pushing and ShouldPush for Pulling is not quite accurate
but probably good enough for now.
