Raymond Carl

I checked a few things: 1) On the websocket protocol level, the Ping / Pong frames between the WSConnection class and the binance websocker server are working even after the...

Hi @cardosofede : I deleted my previous message because I thought I found the issue, but still happened. I still think that there may be an issue with how _execute_cancel...

@pulkitsharma + @cardosofede : I tried today with the changes, and I still get the same problem after about 2 hours. I took the new binance perpetual derivative class from...

@cardosofede: From what I've seen, the order is actually placed on the exchange and is cancelled ok. The problem is that the current state of order tracking used by the...

@cardosofede : Yes, binance perpetuals for me. That's why I was saying that I think this could be a very difficult problem to find because in theory, it should affect...

The class hierarchy for this whole application has been very confusing for me due. I created this so that I don't have to keep looking for the references over and...

One thing I see that seems strange to me is that the binance perpetual connector does not implement the OrderCancellation event like bitmex does. Is it possible that the order...

@amitds1997 : Yes, I agree on the process for the actual cancellation of the order. For the strategy's order tracker though, I think something has to call stop_tracking_limit_order for the...

Ok, now this is starting to make more sense to me. A big question for me now is, "why are any orders at all reflected as canceled if the binance...

I'm going to implement the order cancellation event in the binance perpetual connector locally and let it run while I try to understand how the strategy's version of of the...