Closed hiliev closed 1 year ago
similar here when using just one depth stream
similar here when using just one depth stream
Could you explain that? depth stream is not using a listen key...
I set the interval from 30 to 10 min in the next release.
But we definitely have to improve this!
Any news here? Did the last update avoid this issue?
Looks like bringing the ping interval down to 10 mins has solved the issue for me.
Cool! We can do it better if needed. lets look how this works long term.
I close this, please reopen or open a new one if needed.
Version of this library.
1.41.0
Solution to Issue cannot be found in the documentation or other Issues and also occurs in the latest version of this library.
Hardware?
VPS or other cloud hosting
Operating System?
Linux
Python version?
Python3.8
Installed packages
Logging output
Processing method?
stream_buffer
Used endpoint?
binance.com-futures
Issue
If an error occurs while posting the listen key keep-alive ping, the error is silently ignored, the keep-alive is considered successful, and the failed operation is not retried. As a result, the listen key expires before the next scheduled ping. The library then keeps posting keep-alive pings to the now defunct listen key.