* Adds internal access to materializer before initialization (#25324)
* Implements new actorRef source based on graph stage (#25324)
* Removes obsolete actorRef source (#25324)
* Improves backwards compatibility with old implementation (#25324)
* Removes dedicated new subclass for materializer access again (#25324)
* Improves implementation (#25324)
* Finalizes implementation (#25324)
* Small improvements to API and documentation (#25324)
* Completion strategy as a replacement for poison pill (#25324)
* Adding more tests and updating the documentation (#25324)
* ⇒, →, ←
* because we don't want to show them in documentation snippets and
then it's complicated to avoid that when snippets are
located in src/test/scala in individual modules
* dont replace object `→` in FSM.scala and PersistentFSM.scala
* Add CopyrightHeader support for sbt-boilerplate plugin.
* Add CopyrightHeader support for `*.proto` files.
* Add regex match for both `–` and `-` for CopyrightHeader.
* Add CopyrightHeader support for sbt build files.
* Update copyright from 2018 to 2019.
* Optimize flatMapConcat for single element source, #25241
* Grab the SourceSingle via TraversalBuilder
* Also handle the case when there is no demand
* don't match when mapMaterializedValue and async
When a Success is received, call onCompleteThenStop instead of just
context.stop; that takes care of the completion logic instead of just
stopping the actor and leaving the stream going.
Add test to ensure the stream materializes on Source.actorRef receiving
Status.Success
Remove tests around stream completion behaviour in response to
PoisonPill - as well as these tests not correctly demonstrating that the
completion was passed on downstream, they describe behaviour which was
previously incidental and is no longer accurate.
Update the docs to reflect that PoisonPill should not be used on the
actor ref as this scenario will necessarily result in bad behaviour as
it will be unable to signal the completion downstream.
Make a few grammar fixes and remove some trailing space while updating the
docs.
* 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
* 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
* Change more general factories to private
* Typed Streams docs
* Remove BoxedUnit from Java Api
* Use JavaPartialFunction in Java examples
* Doc wording improvements, formatting fixes, no verification diagrams
+str #24229 remove protobuf changes, which do not need to be made in this PR
docs
moved things
config object
subscription timeout confifmed working, also, attributes
document attributes for sub timeout
tests for the source also failing when it should
additional demand test
implemented protection from materializing "in cycles"; would be nice in
types but that breaks the niceness of use of the types
SinkRef/SourceRef...
cleanup
no idle timeout built in, can use the Timeout stages
more docs
simplest change to prevent exposing SinkRef => SourceRef => SinkRef cycle
Things to decide:
* is it ok to require using `getSource` / `getSink` as Java API, is there better naming?
* where should the constructors go? I'd say just in regular javadsl/scaladsl `Source`/ `Sink` objects
move constructors to {javadsl,scaladsl}.{Source,Sink} companion objects
Remove now useless "canMaterialize" field
Separate stage (implementation) from ref (wrapped actor ref) to make it clearer what is serialized
Clarify that partner refs are not optional in on-the-wire interfaces
minor cleanup in SourceRefStage
Renamed the stages but questionable if that really helps ;)
cleanups, better docs
cleanup, fix docs compilation
fix mima
got rid of Futures in the materialized values of stream refs
Instead of renaming - deprecating and documenting
Renaming defaultInitialAttributes to defaultAttributes and adding docs
Tests passing
More work on using attributes for the attribute settings in ActorMaterializerSettings
Mark some attributes as mandatory and provide a smoother access w/o allocation for those
Another warning notice
MiMa filters
Part of the review adressed
Incorrect rebase fixed + formatting
Review feedback adressed
Formatting ...
* Do not try to submaterialize inner source when outer stream already cancelled #23656
* Use StreamDetachedException
* Sleep a little
* Updated exception text
* these must also be included via setAttributes because
because it will create island for async (dispatcher attribute)
* better actor name of GraphStageIsland, we need it in tests for
lookup of the actor
* this unlocks OutputStreamSourceSpec and InputStreamSinkSpec
