- What version of bluebird is the issue happening on? 3.3.5
- What platform and version? NodeJS 5.7.1
Promise.map() takes as a third parameter an options object accepting a single property to define the iteration concurrency limit. Because there is only one option I often mistake this object as a concurrency argument and provide an integer instead of the right object.
Bluebird silently ignores the bad parameter and keeps an infinite concurrency witch causes unknown stress to the server if iterating over a huge dataset. It should throw an exception if the parameter is truthy but not an object to avoid such mistakes.
Promise.map() takes as a third parameter an
optionsobject accepting a single property to define the iterationconcurrencylimit. Because there is only one option I often mistake this object as aconcurrencyargument and provide an integer instead of the right object.Bluebird silently ignores the bad parameter and keeps an infinite concurrency witch causes unknown stress to the server if iterating over a huge dataset. It should throw an exception if the parameter is truthy but not an object to avoid such mistakes.