-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RuntimeWarning: coroutine 'StreamConn.close' was never awaited #15
Comments
@stabless did you ever figure this out? |
1 similar comment
@stabless did you ever figure this out? |
I am getting a similar message. Does anyone know how to debug this? Getting current ticker data... |
BlueMistTrekker, I am getting the same error. Let me know if you find a solution. |
Interesting problem - any ideas what is causing this ?
354/354
Success.
Watching 354 symbols.
WARNING:root:code = 1000 (OK), no reason
:375: RuntimeWarning: coroutine 'StreamConn.close' was never awaited
conn.close()
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
Cannot close a running event loop
WARNING:root:code = 1000 (OK), no reason
Cannot close a running event loop
WARNING:root:code = 1000 (OK), no reason
Cannot close a running event loop
WARNING:root:code = 1000 (OK), no reason
Cannot close a running event loop
WARNING:root:code = 1000 (OK), no reason
Cannot close a running event loop
WARNING:root:code = 1000 (OK), no reason
Cannot close a running event loop
WARNING:root:code = 1000 (OK), no reason
Cannot close a running event loop
WARNING:root:code = 1000 (OK), no reason
Cannot close a running event loop
WARNING:root:code = 1000 (OK), no reason
Cannot close a running event loop
WARNING:root:code = 1000 (OK), no reason
Cannot close a running event loop
WARNING:root:code = 1000 (OK), no reason
WARNING:root:server rejected WebSocket connection: HTTP 429
Cannot close a running event loop
WARNING:root:code = 1000 (OK), no reason
WARNING:root:server rejected WebSocket connection: HTTP 429
WARNING:root:server rejected WebSocket connection: HTTP 429
Cannot close a running event loop
Cannot close a running event loop
The text was updated successfully, but these errors were encountered: