Dustin C. Hatch
e92d8c9cef
Apparently, the `AsyncReceiver` stream produces nested `Option` objects. The outer is `None` if "the stream is exhausted," which is somehow different than the connection being closed; the inner `Option` is `None` in that case. We were originally ignoring the inner `None`, but just causes the async task to go into a busy loop when connection is closed. We need to break out of the loop there instead.