Krypto-trading-bot: Bitmex websocket API update

[gusiri]

Recently, I found out that the bot keeps sending repeated (and infinite) orders for bitmex,

and I guess the reason is due to bitmex's websocket API update on Aug 24.

Any idea on this?

source: https://blog.bitmex.com/api_announcement/change-to-updates-on-the-order-feed-for-new-and-triggered-orders/

---

Order of messages on the order Websocket API feed for new order requests before this change (2 messages are sent):

• ordStatus=New, workingIndicator=0b

• ordStatus=New | Filled | PartiallyFilled | Canceled | Rejected, workingIndicator=1b | 0b

Order of messages on the order Websocket API feed for new orders after this change (1 message is sent):

• ordStatus=New | Filled | PartiallyFilled | Canceled | Rejected, workingIndicator=1b | 0b

---

Order of messages on the order Websocket API feed for triggered orders before this change (2 messages are sent):

• ordStatus=New, workingIndicator=0b, triggered=StopOrderTriggered

• ordStatus=New | Filled | PartiallyFilled | Canceled | Rejected, workingIndicator=1b | 0b, triggered=StopOrderTriggered

Order of messages on the order Websocket API feed for triggered orders after this change (1 message is sent):

• ordStatus=New | Filled | PartiallyFilled | Canceled | Rejected, workingIndicator=1b | 0b, triggered=StopOrderTriggered

[ctubio]

you are totally right; sorry for taking me so long

[Corfucinas]

commenting so I can follow the discussion (turned off my bot when this started happening).

[gusiri]

So glad @ctubio is back!