-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Task already disappeared teardown error? #46
Comments
This may have something to do with a race when using async generators wrapped by a portal where the far end actor errors and closes the connection, the channel get's de-allocated by the current actor, and the generator is just left hanging waiting on an already closed connection to recv data because the queue / consumer side hasn't been alerted of the break. I'm not sure why there isn't an error getting raised in the msg loop but it's probably something stupid. |
Well here's the second issue in more detail with logging from
|
I'm not sure how this ever worked but when a "fake" async gen (i.e. function with special `chan`, `cid` kwargs) is completed we need to signal the end of the stream just like with normal async gens. Also don't fail when trying to remove tasks that were never tracked. Fixes #46
I got this testing out the new options data feed in
piker
:Setup was:
pikerd
as standalone daemon-actorpiker monitor
piker
test suitepiker monitor
pikerd
bailed as above...The text was updated successfully, but these errors were encountered: