Describe the bug
When creating a ThreadedDepthCacheManager and starting a future depth socket (start_futures_depth_socket), the limit parameter is not being passed deep enough. So the subscription message to Binance uses the default "10" value.
This isn't happening if starting a spot depth socket.
Describe the bug When creating a ThreadedDepthCacheManager and starting a future depth socket (
start_futures_depth_socket
), thelimit
parameter is not being passed deep enough. So the subscription message to Binance uses the default"10"
value.This isn't happening if starting a spot depth socket.
To Reproduce symbol = 'BTCUSDT'
Expected behavior The limit parameter should be taken in consideration when subscription to futures book updates.
Environment (please complete the following information):