I'm trying to migrate my app's client to trio-websocket, but have a test hanging at client send_message(). It appears to be blocking the scheduler, because a trio.fail_after() before the call has no effect. Keyboard interrupt does kill it.
I need to dig into it, but the behavior seems similar to previous mysterious hang issues on OS X. (Last one cleared up by upgrading wsproto.)
I'm trying to migrate my app's client to trio-websocket, but have a test hanging at client
send_message()
. It appears to be blocking the scheduler, because atrio.fail_after()
before the call has no effect. Keyboard interrupt does kill it.I need to dig into it, but the behavior seems similar to previous mysterious hang issues on OS X. (Last one cleared up by upgrading wsproto.)