-
-
Notifications
You must be signed in to change notification settings - Fork 166
Unhandled exception futures.TimeoutError() #221
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
Comments
Hello, anybody here? I get this error constantly and it is very annoying. Does it happen to anyone else too? What should be done to fix it? |
In old python versions i never had that issue in 2 years. We have similar new open issues related to this issue. Please add answers to the questions we ask when you created this new issue. This information help me to solve this issue. I am planing a bigger release at the end of this year with a fix for this bug. |
Fixed |
stream_buffer or process_stream_data? |
Sorry, I don't know what is this.
|
Then you use the stream_buffer! Thanks, this infos help! |
Could you please point me to the docs which explain what is the difference between stream_buffer // process_stream_data ? |
stream_buffer info: https://github.com/oliver-zehentleitner/unicorn-binance-websocket-api/wiki/%60stream_buffer%60 process_stream_data is a call_back solution: https://oliver-zehentleitner.github.io/unicorn-binance-websocket-api/unicorn_binance_websocket_api.html?highlight=process_stream_data (just scroll down a bit to the description of the parameters) |
Hello Oliver, |
Hello! I understand your problem and your needs, i am just very busy atm :/ I think the queue of awaits is getting to long and then timeouting. How many subscriptions do you have? You must know, Python is really cool, but it sucks with concurrency, even if you have 6 cpu sockets, each with 16 cores. You just use the resources of one cpu core. Read here about the reason: https://realpython.com/python-gil/ I wanted to study your log file, but did not find it. Wasnt it already posted? Your python version is well tested with UBWA, i guess the root cause for the error you get is an overloaded application. I can release a fix to reconnect, but you would still not be stable in cause of all the unneccessary reconnects. There is no version without asyn.io and never was... |
I have ~50 different streams. That's why I asked this question: #220 Is it of any use if I try to pack these 50 subscriptions in single stream? So there is no old version that I can fall back to in order to rescue the situation temporarily? |
Here is the log file: |
The link does not work. you can drag&drop the log file to the text box of a new comment. |
You have 50 streams with one subscription each? If yes, make one stream for each channel like trade, kline_1m, ... and use them for up to 1024 subscriptions per stream. Futures is 200 subscriptions per stream: https://github.com/oliver-zehentleitner/unicorn-binance-websocket-api/wiki/Binance-websocket-endpoint-configuration-overview |
Uh oh!
There was an error while loading. Please reload this page.
Check this or we will delete your issue. (fill in the checkbox with an X like so: [x])
Select one:
Environment
What kind of internet connection do you have?
Average system load (CPU)
Hardware specification
Operating System? (include version)
Options
Which endpoint do you connect?
Python Version Requirement
Exact Python Version?
Pip Version?
Dependencies
https://pastebin.com/6uDicgT9
UNICORN Binance WebSocket API Version?
Description of your issue
The text was updated successfully, but these errors were encountered: