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
As far as i understand - runIntoPubSubScoped should be terminated once the Effect.scoped(program) has finished, then the forked effect will be completed with void result, then there will be no job in event loop, so NodeJS process will be terminated.`
What do you see instead?
NodeJS process hangs forever.
Additional information
I thought maybe it is because the stream is still running, so i added .pipe(Stream.tap(Console.log)), but there are no logs in console.
The text was updated successfully, but these errors were encountered:
It is because the fiber hasn't started when it hits Effect.awaitAllChildren, if we ensure the fiber has started first it will work: https://effect.website/play#83b4743a0952
It is because the fiber hasn't started when it hits Effect.awaitAllChildren, if we ensure the fiber has started first it will work: https://effect.website/play#83b4743a0952
What version of Effect is running?
3.1.5
What steps can reproduce the bug?
What is the expected behavior?
As far as i understand -
runIntoPubSubScoped
should be terminated once theEffect.scoped(program)
has finished, then the forked effect will be completed withvoid
result, then there will be no job in event loop, so NodeJS process will be terminated.`What do you see instead?
NodeJS process hangs forever.
Additional information
I thought maybe it is because the stream is still running, so i added
.pipe(Stream.tap(Console.log))
, but there are no logs in console.The text was updated successfully, but these errors were encountered: