GitHub user gaeljw added a comment to the discussion: [Pekko Streams] Best practice for streaming from a resource that can take several seconds/minutes to start offering an element
TBH I moved on because I was not able to identify the difference between my minimal example above that works (at least its async variant) and the real code, that even async-ified did not work. I may come back to this later but this is now much less of an issue for me because the underlying blocking resource (database) now answers much faster than before. GitHub link: https://github.com/apache/pekko/discussions/1572#discussioncomment-11727651 ---- This is an automatically sent email for notifications@pekko.apache.org. To unsubscribe, please send an email to: notifications-unsubscr...@pekko.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org For additional commands, e-mail: notifications-h...@pekko.apache.org