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
The way broadcasting to taps and extensions works currently is not safe. It should support backpressure, but currently messages just pile up in a big queue, leading to possible memory leaks and other unpleasant issues. This needs a thorough rethink. There is a lot of discussion available on the issue of broadcasting in the trio community as well.
Naive attemp to make broadcasting safer has been added in the safe-broadcasting branch. It simply wraps the send loop in a separate nursery, which will have the effect of not allowing the source iteration to continue until all sends have completed.
The way broadcasting to taps and extensions works currently is not safe. It should support backpressure, but currently messages just pile up in a big queue, leading to possible memory leaks and other unpleasant issues. This needs a thorough rethink. There is a lot of discussion available on the issue of broadcasting in the trio community as well.
See for instance: python-trio/trio#987
The text was updated successfully, but these errors were encountered: