gael-ft

Hi @pe-st, thanks for the project ! Any chance this issue (and related PR) will be merged / closed ? I believe this would be useful in various use cases

> Seems should add another parameter eager too. When true will complete / fail the stream when upstream fail. Not obvious to me. Goal `flatMapConcat` is to keep elements ordered....

@He-Pin I might be a bit too much use case centric (i.e. S3 object upload where we don't want any missing part). > If when materilization, the upstream is Source.failed...

Hi @johanandren Thanks for the review ! > Note that trying to control if the upstreams pre-fetch like you try to do is tricky since the sources could always contain...

Well, that being said, don't like much `ranges.mapAsync(parallelism)(range => fetchEntireRangeIntoFutureByteString)`. If I am correct, it means no ByteString will be pushed downstream until the range is completely fetched, which would...

Just want to be sure to fully understand the issue to fix it correctly (and to know what I should take care of in the future 😉): > Note that...

> All the range requests are done immediately on materialization Ok thanks clear enough to me now.

Hello @khushail, Ok thanks for linking, didn't find it ... Looks to be release with in v2.163.

Interesting, didn't know `contextvars` ! Effectively, looks like it solve this example. Was able to do something like: ```python my_context_var: ContextVar[MyContext] = ContextVar("my_context") class MyContainer(containers.DeclarativeContainer): my_context = providers.Callable(my_context_var.get) some_service =...

Hi @bblommers, thanks for reviewing my proposal ! > How would you feel about keeping the existing endpoint, but adding another field to the supplied results to indicate whether a...