ring hangs when attempting to use websockets with :async? true about ring HOT 3 CLOSED

Thanks for the report! I was wondering how this could have gotten past the tests, but it turns out this is an omission in the test suite; websockets are never tested with async handlers!

I'll plug the hole in the test suite and release a fix this weekend. Looks like it should just be a case of changing:

(upgrade-to-websocket request response response-map)

To:

(do (upgrade-to-websocket request response response-map)
    (.complete context))

from ring.

I can confirm that implementing this monkey patch makes the async response work immediately!`

from ring.

Thanks in advance @weavejester

from ring.