* Remove OptionVal workaround
* Revert "Avoid pattern-matching on OptionVal since Scala 2.13 allocates when checking the pattern"
This reverts commit f0194bbc1ad43ac2c79bf156bfe91adf7fd5e538.
* Revert "Optimizes retrieval of mandatoryAttributes by removing potential allocation of OptionVal"
This reverts commit 165b0e0d5c057965e37418299061bdf48c33fc44.
* I think it was a thread starvation problem because next test step could
start before the previous pool had been terminated.
* Many (at least 5) threads are blocked in this test and AkkaSpec defines a max of 8.
Cannot be observed from the SubSink side if the materialization failed or the
running stream already cancelled, so just ignore the sub-sink cancellation in the
case where the sink is already cancelled.
Previously it included a coarse grained Java reformat which it seems was never
quite worked through (reformatting generated sources etc), so go back on that,
and make sure verifyCodeStyle is exactly what we require for PR validation to pass
(and that it does not diverge)
* "must send elements downstream as soon as time comes"
* it failed with perThrottleInterval:
Map(0 -> List((0,1), (499,2)), 2 -> List((1000,3), (1499,4)), 3 -> List((1999,5)))
* round the interval groups
* use dilated
* Use apidoc directive in general/configuration.md (#22904)
* refer to ConfigFactory
* use name Typesafe Config library
Co-authored-by: Arnout Engelen <arnout@engelen.eu>
Co-authored-by: Arnout Engelen <arnout@engelen.eu>
* Value not def for underlying state store
* Ooops forgot to remove parens
* Remove type param
* Other type
* Fix types
* Similar reference wrapper issue
* Trailing spaces removed
* DeathWatchNotification (the remote system message for Terminated) is
supposed to be delivered after other ordinary messages.
* The flush mechanism didn't take the inbound lanes on the receiving side
into account. That could case DeathWatchNotification to overtake
other messages that are in flight in the inbound lanes.
* This makes sure that the Flush is copied to all inbound lanes and
the sender of the flush can wait for all expected acks before sending
DeathWatchNotification.
* Adds expectedAcks to FlushAck in i wire protocol compatible way to
support rolling updates.
* take it from testkit settings instead of hard coded
* dilate it
* it's still somewhat confusing since we have both
classic and typed testkits and they dilate the default
timeout differently, but don't want to change too much
