* it was noticed in Source.fromIterator depending on where the
iterator throwed exception
* fromIterator, as many other things, is implemented with
statefulMapConcat
* supervision was only used for exceptions in onPush and not
in onPull, added it there also
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
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 ...
* =str #22880 fix mapAsync racy failure handling
* =str #22881 test also resume case for throwing mid-stream mapAsync
* address review feedback, the handle calls must be exactly like that
* added a failing test to demonstrate a bug in groupedWeightedWithin with zero cost function
* fixed the bug by adding a flag indicating if there are elements in buffer, and using it instead of totalWeight in case onTimer is called
* #22506 Mark materializer extension as @InternalApi
* #22506 Added missing annotations on internal apis in the fusing package
* #22506 Missing annotations in io package
* #22506 Add internal api annotations in impl package
* #22563 more hiding of the classes in the impl package
* #22563 Formatting fixes
* #22506 Fix private access in stream tcl tests
* Add comprehensive tests
* Add documentation
* Damn comma after rebase
* Add documentation for foldAsync and scanAsync
* Rename aggreator and aggreating to current
* Remove out availability check
* Revert removing out and some refactors
* Formatting documentation
* Use after instead of Promise in test
* Use package reference to after and some refactoring
* fail fast in mapAsync for completed failed future, #21318
* the callback was not run until todo == parallelism or the sync
event limit was reached, and that can be a problem if upstream
stages are slow (noticed this for a blocking Kafka producer stage)
* skip callback for completed futures
* fix callback allocation
