-
what is this? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
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. |
Beta Was this translation helpful? Give feedback.
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.