* automatic throttle burst size, #24699
* throttleEven used maxBurst=Int.MaxValue, which in practise resulted
in no throttling at all at high rates
* The original problem that throttleEven tried to solve was that when
the throttle rate (cost / per) was high the cost of scheduling
dominated and became much lower than the given rate, if 0 or low
maxBurst was given. Difficult for user to know what maxBurst to use.
* In fact, that was already the case for rates > 30/s.
* This is fixed by automatically adjusting the maxBurst for higher
throttle rates in a new throttle overload that doesn't include
maxBurst parameter
* Also skipped the mode parameter for that variant since Shaping is
what almost always is what you want, and otherwise you can use
the full signature with a good maxBurst
* Deprecated throttleEven, since it is the same. Also fixed the
implementation of throttleEven to use the automatic burst size,
since Int.MaxValue is not useful at all.
* Adding additional details to the auto-downing section of the documentation to indicate the consequences of using it
* Slight rewording based on PR feedback.
* Remove default parameters in doc journal
Making sure the examples are explicit about them
* Don't rely on default parameters in docs
As those default parameters might not be present for all implementations
* remove unrelated changes from PR
* Update BehaviorTestKitSpec.scala
timeout is explicitly a message of Command
persitAll and chainable side effects work well
more tests pasing
additional sanity check that mutable behaviors work as expected
unstashing needs to "loop through" the AdapterActor otherwise Stopped
won't work
solve unstashing/stop issue, by not randomly init()ing, but unstashing
snapshotting works
all tests green
rebased
nicer log source
remove IncomingCommand wrapper, we dont need it
no need for shared counter
remove not needed methods and state
more state cleanup, using Behaviors.same
reminder that we DO need that same alias, since stash does not work with
the Behavior.same
introduce config for stash buffer
stopping now works after persisting
compile fix
cleanup
reduced number of adapter styles needed for co-existence of persistence
final cleanup done, less passing around 40 objects, carriers provided
now
* deduplicate logic for IODispatcher #24604
* introduce a resolveDispatcher helper in ActorAttributes
* mention akka.stream.materializer.blocking-io-dispatcher instead of akka.stream.blocking-io-dispatcher in scaladocs
* fix a flaky test
* cosmetic changes in the touched files
* move resolveDispather helper to the Dispatcher companion object under a new name resolve
* filter out mima warning
* fix mima excludes after the 2.5.11 release
* address review comments
* update stream-io.md with the correct dispatcher config key
* mark ActorAttributes.Dispatcher#resolve as internal API
* use the dispatche config key in ActorMaterializer
* add private[akka] to the resolve methods
* Java specific testkit
* Separate all the APIs
* Dilate the default timeouts
* TestKit -> ActorTestKit to be consistent with BehaviorTestKit
* Only have stuff in packages expected for this module
* Auto testkit-system-naming that works (verified)
* Separate actually working apis for manual timer
* More docs
* Separate apis for BehaviorTestKit effects
* Moved the example tests into the testkit, added samples for JUnit/ScalaTest
* TestKitJunitResource: No need to explicitly provide class, also overload for just custom config
progressed with cleanup, removing the same thread exec context is
weird... causes issues :-/ Need to debug more, could be that some race
also exists in mapAsync then :\
WIP
finish ask impl via watch stage
mima
consistency spec
fix paradox, and fix adding ask/watch to javadsl source
follow up review
* Issue 24519: Created method lazilyAsync for both DSLs and adds section in docs.
* Issue 24519: Changes according to code review
* Issue 24519: Added unit tests
* Update LazilyAsyncSpec.scala
* Issue 24519: Added copyright
