Alan Wu

`generate` seems to conflict as well need to use `nx run api:generate`

Same problem

run `yarn gen`

Experience this issue as well

bump

Will `setTimeout` cause overhead? - is there a way to not check this every time I use the client

Same issue

Same issue - rate limit from watchOrders - looks like it's calling `https://api.bybit.com/v5/asset/coin/query-info?`

Can we use this to prevent the issue https://github.com/coopernurse/node-pool/issues/175#issuecomment-501826583

Is this solved? I am doing this after `clear` ```js for (let index = 0; index < this.pool._availableObjects.length; index++) { this.pool._availableObjects.shift() } ``` Should `clear` also destroy resources in `ALLOCATE`...