Levin Keller
Levin Keller
Is this issue still open?
@braydonf Is this not someone "critical" and should be fixed asap? Or am I mistaken on the severity?
Please remove the includeGuard.
I was able to reproduce. The issue is, that I do something like this. ``` js BitcoreNotifier.prototype.transactionHandler = function (transactionBuffer) { var self = this; var tx = new Transaction().fromBuffer(transactionBuffer);...
That might mitigate, but I still have no control of how many queries are coming at the same time through insight-api or some other service...
Thank you, @braydonf. You can close this or keep it open as a feature request. Would appreciate a global queuing. Btw. I will try `async.queue` for anyone doing the same....
Something else: As far as I understand queries to the API now immediatly trigger queries to bitcoind (rpc calls). Like "additional transaction information" on the /tx endpoint. Does this scale?...
I just made an issue here: https://github.com/bitpay/insight-api/issues/492 Getting the error from the insight api just by running multiple requests in parallel. As the current implementation is passing each query on...
What do you mean by this? Multiple bitcoind nodes? I can overload your deployment on https://insight.bitpay.com/api with just 200 queries in parallel... And by overload I mean that others will...
Go back to older insight api version (and old bitcore node) or query less and / or slower and repeat failed requests.