Habib Alkhabbaz

Hello guys @uhliksk @chrisleekr As always, you both have good thoughts. From my perspective, I can see this idea as a double-edged sword because when we cancel the order when...

@uhliksk Your explanation makes sense to me. I think that the order executed too much fast for @Rayn0r And for the second possibility, yes, there is a priority option for...

@uhliksk Sure it's better than setting priority for our case! However, I just started to rethink about this. What I found is we will not get any benefit from setting...

Hello @uhliksk The current queue implementation is just pushing an empty job to the symbol queue and its listener will execute the trailing trade steps. No matter if we queue...

Hello @uhliksk I think my example was not clear. I just updated the example to be more clear. Sorry for that. Each symbol can have only 1 concurrent job running....

@uhliksk You are right 💯 That is one reason. We have to refactor this to force handling open orders. However, I think we can just keep the queue to work...

> @habibalkhabbaz I agree but also I'm just thinking if we actually still need the symbol locking. If we queue `executeTrailingTradeIndicator` in the same queue with `executeTrailingTrade` then we will...

Hello @uhliksk Do you see any error log? Regarding the Binance websocket implementation, it has a reconnect mechanism and it should reconnect by default https://github.com/ViewBlock/binance-api-node/pull/49 If you have any log...

@uhliksk I will try to disconnect when I have time and I will report back to you. Maybe we have to apply a fix for this.

Hello guys @uhliksk @chrisleekr @Rayn0r Sorry for the late reply. As mentioned by @chrisleekr, that would solve the problem. It was removed in the latest releases due to massive refactoring....