Re: [akka-user] Debugging postStop cause within a custom stage

As a follow-up to this, the problem was of course of my own creation. However, what wasn’t obvious to me was that the default behaviour of an InHandler is to complete the stage once the upstream is completed. The API doc states: Called when the input port is finished. After this callback

Re: [akka-user] Debugging postStop cause within a custom stage

I’m wondering if I'm seeing a problem related to https://github.com/akka/akka/issues/23111 . My `Source.single` completes quite quickly. I also have a custom stage with an async callback. I have observed that the stage registers as being completed wh

Re: [akka-user] Debugging postStop cause within a custom stage

> On 3 Nov 2017, at 8:30 am, Patrik Nordwall wrote: > > Could it be that the materializer is shutting down? > “Abrupt termination” > /Patrik I don’t *think* so, as I should see that exception manifest itself in the test: https://github.com/huntc/landlord/blob/8671d90dba7247db517ef21b64b84d65908

Re: [akka-user] Debugging postStop cause within a custom stage

Could it be that the materializer is shutting down? “Abrupt termination” /Patrik tors 2 nov. 2017 kl. 04:29 skrev Christopher Hunt : > Hi there, > > I've got a situation where I observe a postStop being called within my > custom GraphStage prior to when I'd expect. I'm sure Akka is doing the > ri

[akka-user] Debugging postStop cause within a custom stage

Hi there, I've got a situation where I observe a postStop being called within my custom GraphStage prior to when I'd expect. I'm sure Akka is doing the right thing but, what's the best way to debug what is causing the postStop? My understanding is that the input and output connections should al