You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the documentation of connect I would expect both s1 and s2 to be closed after closing s2, even without specifying the upstream? flag as s2 is the only downstream sink. However, even when :upstream? is true, s1 stays open.
Could you please take a look if is either a gross misunderstanding on my side or a bug?
The text was updated successfully, but these errors were encountered:
dm3
changed the title
:upstream? true in `connect doesn't seem to work
Upstream flag in connect doesn't seem to work
Dec 10, 2015
The upstream closing behavior isn't immediate, it will only take effect when s1 tries to convey a message to s2 and fails because it's closed. I'l think about how to make the documentation clearer on this point.
I'm going to close this issue, but feel free to ask any further questions you have.
Given the following:
the test fails as
s1
is still open.According to the documentation of
connect
I would expect boths1
ands2
to be closed after closings2
, even without specifying theupstream?
flag ass2
is the only downstream sink. However, even when:upstream?
is true,s1
stays open.Could you please take a look if is either a gross misunderstanding on my side or a bug?
The text was updated successfully, but these errors were encountered: