Unhandled rejection from `.map()` and `.filter()` in v3.5.1

Please answer the questions the best you can:

1. What version of bluebird is the issue happening on?

3.5.1

1. What platform and version? (For example Node.js 0.12 or Google Chrome 32)

Node 6.12.2, Mac OS 10.12.6

1. Did this issue happen with earlier version of bluebird?

No. Issue not present in bluebird 3.5.0.

---

Chaining .map() or .filter() on to a rejected promise leads to an unhandled rejection, even when .catch() handler is attached further down the chain.

Promise.reject( new Error('foo') )
    .map( () => {} )
    .catch( () => {} );

With bluebird v3.5.1, the above produces Unhandled rejection Error: foo. In v3.5.0 no unhandled rejection is created.

I assume is caused by https://github.com/petkaantonov/bluebird/commit/48c8591c0ad3fc6a8f6dc38956fe6a08dd0b617f but I can’t understand why!

Don’t know if this is related to https://github.com/petkaantonov/bluebird/issues/1468.

[aviranco]

I’ve experienced this issue as well. What is the status of this issue? the fix is planned to be merged soon?

[overlookmotel]

Please see PR #1489 which fixes this.