Connections not properly cleaned up about aioslsk HOT 3 CLOSED

There's multiple problems here:

When disconnecting all the potential parents tasks get cancelled, but the cancellation is not awaited. Cancellation doesn't actually disconnect the connections already established

Next step is to disconnect all other distributed connections, perhaps we run into a problem here because the cancellation is not awaited. Either way the tasks are fire-and-forget which isn't recommended.

The reason that it's fire-and-forget is because the cancellation happens when we receive the message. If we need to await the cancellation and disconnecting we will temporarily block receiving messages from our parents if disconnecting takes a while

from aioslsk.

It is also rather odd that the connection remains open, or at least it appears that way.

from aioslsk.

Closing ticket, haven't seen this issue occur any more after the fixes referenced. If it comes back then the ticket can be re-opened or a new one created

from aioslsk.