Watch_orders api with newUpdates or not with newUpdates both have bugs.

[angrymilk]

Operating System

linux

Programming Languages

Python

CCXT Version

4.1.86

Description

watch_orders with newUpdates will get error when openordres are bigger than limit, because ArrayCacheBySymbolById deletes order with which is earlier, if the earlier order is still open, but the older older is ended, the earlier order will lose status.
watch_orders without newUpdates also will get something wrong, the reason is about the code below.

If self.futures[message_hash] is not ready from where the watch_orders is called, this message will get lost.

Code

  def resolve(self, result, message_hash):
        if self.verbose and message_hash is None:
            self.log(iso8601(milliseconds()), 'resolve received None messageHash')
        if message_hash in self.futures:
            future = self.futures[message_hash]
            future.resolve(result)
    
            del self.futures[message_hash]
        
        return result

[sc0Vu]

@angrymilk any script that we can reproduce this?