James Fleming

@quorak Check the new updated release, which has an update dependence on XChange.

@stepanurban Can you check if this still occurs with the 4.3.11 release?

@declan94 Excellent - if you could possible start with #191 that would be great!

Quick update - Here are the current open PRs for BitMex 2020/04/04 - This list is now stale ~~#267~~ ~~#244~~ ~~#233~~ ~~#218~~ ~~#180~~

@Spyros-Stylianou It appears they have been closed as they are all stale in terms of progress. Here an updated list of issues that could be re-opened if they were updated...

@szd116 Is this question still relevant - also could you specify which exchange you are using as it differs across them.

Need more info to know if the websocket endpoints are working correctly.

This bug is several months old - needs testing and validating to see if it still bug. It is likely it was a server side bug that may have been...

[XChange #1554](https://github.com/knowm/XChange/issues/1544)

I recommend a similar approach to #205 - essentially deprecate the old api and produce a new api, under a new package/project for v3