race condition during auth about ccxt HOT 4 OPEN

Hello @untoreh, thanks for reporting it, we will take a look and let you know.

from ccxt.

@untoreh Can you post the complete snippet? (especifically what you do with coro1/coro2).

But yes, I see how this can be a problem when they're triggered "in parallel". A lock does not really apply here since we're running everything on the same thread, right?

from ccxt.

@untoreh Actually using this snippet i can't reproduce the issue:

    markets = await exchange.load_markets(True)
    exchange.verbose = True
    sym = 'BTC/USDT'
    await asyncio.gather(
       e.watchMyTrades(sym),
       e.watchOrders(sym),
    )

from ccxt.

I could reproduce it in my bot, but I am not sure which exchange functions were being called at the same time (maybe also createOrder and something else...)

I don't know what's your convention here, I suppose the user should take care of concurrency issues, therefore ccxt shouldn't manage locks, but functions that are not public and called implicitly (like authenticate) probably should

from ccxt.