Skip to content
Discussion options

You must be logged in to vote

This means you're running a piece of long-running blocking code that did not allow the library to send/receive messages on its websocket in the meantime.

You should see if you can replace it with the async equivalent as mentioned in the What does "blocking" mean? FAQ entry, or if this is not possible to do (if you're for example running PIL to generate images) you can run the code in an executor which will by default create another thread to run the synchronous code and return the result to the main thread, without blocking.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@sus2790
Comment options

Answer selected by sus2790
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants